Help ScoutApp Access Issues
Inbox and AI Draft behavior is stable across the board, so we're closing this out. Thank you for your patience while we worked on this one!
Resolved
Outages and recoveries from the services you depend on.
40 incidents
Inbox and AI Draft behavior is stable across the board, so we're closing this out. Thank you for your patience while we worked on this one!
Resolved
This incident has been resolved.
Resolved
The error rate remains within normal thresholds and the issue is now resolved. Further details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22729
Resolved
This incident has been resolved.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
This incident has been resolved, export jobs are complete
Resolved
We are pleased to inform you that the incident affecting our Compute - Instance offering in GRA5/7/9/11 regions has been resolved. <b>Start time :</b> 18/08/2026 14:09 UTC <b>End time :</b> 18/08/2026 15:05 UTC <b>Root Cause :</b> A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.
Resolved
Some newly registered users may have experienced issues logging in to the management console between 13:00 UTC on 17 August 2026 and 14:00 UTC on 18 August 2026.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
Between 16:03 and 16:29 UTC on August 12, some users encountered errors when viewing pull requests, issues, and search results. During this period, about 1.9% of Pull Request requests and 0.9% of Issues requests failed. During a database migration, two indexes were removed while application settings still referenced them, causing affected requests to fail. We detected the issue after the migration reached one database shard and before it progressed to the remaining shards. We restored service by disabling both settings. We are improving safeguards around database migrations and application configuration to prevent similar mismatches from causing errors.
Resolved
Steady throughput for the last 30 minutes. Delay < 5min.
Resolved
The issue has been resolved.
Resolved
Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.
Resolved
Inbound calls are currently operational.
Resolved
We are pleased to inform you that the incident affecting our Storage offering has been resolved. <b>Start time :</b> 17/08/2026 09:31 UTC <b>End time :</b> 18/08/2026 11:33 UTC <b>Root Cause :</b> This incident was caused by a network equipment issue. We apologize for any inconvenience caused and appreciate your understanding.
Resolved
We have concluded our monitoring period and have deemed this incident resolved. Thank you for your patience. If you encounter any further issues, please open a ticket with us at helpdesk@pantheon.io.
Resolved
Shopify integration has been restored.
Resolved
Kimi K3 availability has recovered and the service is operating normally. We have resolved this incident.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved. Submissions to our Contact Sales, webinar/event registration, ZapConnect registration, and AI Leaders Lab forms are working normally again. The issue was caused by our third-party form provider’s daily API limit being exhausted by internal Zapier traffic, which prevented these marketing-site forms from loading and submitting. The upstream limit has been raised, the internal traffic source has been stopped, and form submissions have been confirmed stable. Thanks again for your patience while we were working on resolving that, and if you have any questions, or are running into any other issues, please reach out to our support team: https://zapier.com/app/get-help
Resolved
Between 20:00 UTC and 21:15 UTC on August 17, 2026, a subset of customers using Neon databases in AWS us-east-2 may have experienced delays or failures when performing branch reset and restore operations. A configuration rollout caused these requests to fail on the backend; the Neon Console automatically retried them, so affected requests appeared to hang. The change has been rolled back, and all services are operating normally. Customers may have observed: - Branch reset and restore requests via the Neon Console or API are hanging or taking longer than usual to complete - Requests that did not complete and had to be canceled manually The issue has been fully resolved, and all services are operating normally. We apologize for any inconvenience. If you require further details, please submit a support ticket.
Resolved
All our systems are back online and functional.
Resolved
This incident has been resolved.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
GitHub outage is over and the customizations are going through.
Resolved
Github has resolved their incident.
Resolved
Insights data is good once more. Thank you for your patience.
Resolved
Beginning at approximately 14:50 UTC on August 13, 2026, customers who attempted to provision Linode Kubernetes Engine Enterprise \(LKE-E\) clusters in the IAD2 data center were unable to. We identified that the issue was due to the exclusion of two components in IAD2 in a recent software version upgrade which resulted in an API mismatch. We updated the identified components to bring them in sync with the expected state. This mitigated the issue at approximately 16:00 UTC on August 13, 2026. To prevent this issue from occurring in the future, we are reviewing LKE software update processes to ensure that all included components complete version upgrades before being reintroduced to service during platform software updates. This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing and any information herein is subject to change.
Resolved
Fully recovered by 5:24PM (ET).
Resolved
Services have recovered. We are still working to ingest missing observability data during this period.
Resolved
The GitHub operations should be returning to normal as its service is back online. We’ll keep monitoring for any updates to the incident. GitHub Incident status: https://www.githubstatus.com/incidents/zkxwbgr0cnmx
Resolved
ChatGPT logins should now be working
Resolved
Severity Level: [High] This incident has been resolved. The network issue affecting our us-south-2 region has been fixed, and connectivity to instances, including via SSH and Jupyter, has been fully restored. The region has remained stable since the fix was implemented. In the event you believe your service is still impacted, please open a support ticket and we'll get back to you as soon as possible. https://support.lambdalabs.com/hc/en-us/requests/new Thank you for your patience and understanding during this time.
Resolved
We have received confirmation that an external issue impacting email delivery to Microsoft 365 domains has been resolved. Impacted messages would have received an error stating "5.7.511 Access denied, banned sender" between Friday, August 14th and Monday, August 17th. Any failed messages will need to be resent. Information on retrying messages can be found in our Help Center here: https://help.mailgun.com/hc/en-us/articles/18596982041883-Resending-messages
Resolved