ElasticIssue with Kibana authentication flow
We have identified the root cause and mitigated the issue. Users should now be able to log in to Kibana via the "Log in with Elastic Cloud" button.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
We have identified the root cause and mitigated the issue. Users should now be able to log in to Kibana via the "Log in with Elastic Cloud" button.
Resolved
The issue has been resolved. All affected functionality is operating normally.
Resolved
The top-level domain provider has fixed the underlying problem that was causing this issue. Name resolution has returned to normal.
Resolved
The top-level domain provider has fixed the underlying problem that was causing this issue. Name resolution has returned to normal.
Resolved
The issue affecting Linode Migrations has been resolved. Resize and Migration operations should be operating as normal now.
Resolved
Channel connection issues have been fully resolved and performance is working as expected. Please reach out if you continue to see issues. We apologise for the interruption today.
Resolved
We have successfully resolved the Facebook Lead Ads integration issue that affected our platform from 12:30pm–4:00pm PDT (7:30pm–11:00pm UTC) on June 16, 2026. During this window, customers experienced failures when connecting or reconnecting Facebook Lead Ads and Facebook Pages integrations, and existing Zaps using these integrations failed to execute. We identified this as an upstream issue with Facebook's APIs, which has since been resolved. All affected workflows have been replayed and are now operating normally. If you continue to experience any issues with your Facebook integrations, please try reconnecting your Facebook app connection or don't hesitate to contact Zapier Support: https://zapier.com/app/get-help.
Resolved
Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC20000030](https://community.snowflake.com/s/article/INC20000030)
Resolved
On June 8, 2026, between approximately 06:30 UTC and 08:36 UTC, signed-out users experienced sustained elevated HTTP 504 errors when accessing Pull Requests, Issues, releases, patch diffs, and other related GitHub.com pages. During the incident, approximately 17% of unauthenticated requests to the affected GitHub.com endpoints returned gateway timeout errors, peaking at roughly 34% of requests at around 06:50 UTC. Some GitHub Actions workflows were also affected when they depended on release downloads or related GitHub.com endpoints. The impact lasted approximately two hours and was isolated to unauthenticated traffic; signed-in users were not affected. <br /><br />The issue was caused by a significant increase in abusive traffic to specific GitHub.com endpoints. This degraded our ability to respond to unauthenticated requests, causing requests to queue beyond timeout thresholds and return gateway timeout errors. <br /><br />We mitigated the incident by identifying the anomalous traffic pattern and applying targeted blocks at the load balancer and application layers. Error rates returned to normal and affected services were fully restored by 08:36 UTC. <br /><br />To reduce the likelihood and impact of similar incidents in the future, we are improving automated detection and blocking for these traffic patterns, improving our emergency traffic-blocking deployment path, and evaluating routing changes for endpoints used by both signed-out users and automated workflows.
Resolved
Some users may have been unable to edit or delete messages in certain channels. We identified and resolved the issue. We apologize for how this issue affected you and your business.
Resolved
All impacted services have now fully recovered.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Our Engineering team has resolved the Terraform Registry service degradation. If you continue to experience any problems, please open a ticket with our support team.
Resolved
Downstream dependency Jitpack has resolved their outage and builds are succeeding again.
Resolved
All pending configuration changes have propagated across the CDN.
Resolved
This incident has been resolved.
Resolved
The issue is now resolved and PostHog AI is working normally again.
Resolved
All impacted services have now fully recovered.
Resolved
This issue has been resolved.
Resolved
We experienced a brief service disruption affecting LinkedIn video publishing, which experienced an abnormal rate of unsuccessful posts between 11-2:30pm PDT. Analysis by our engineering team determined that this disruption was caused by a change made by LinkedIn, which has since been resolved. Any posts that were not successfully published during this time can now be rescheduled successfully
Resolved
Connectivity issues are gone now. Intermittent failure is being investigated in the background with the uplink provider, while the Nebius Netowrking team continues to monitor the link closely.
Resolved
The issue affecting sign up and login has been resolved. All authentication services are operating normally. We apologize for the disruption and will share a full write-up shortly.
Resolved
This incident has been resolved.
Resolved
The issue with Observability data ingest for OpenTelemetry data has been resolved. Impacted services have returned to normal operation.
Resolved
The service interruption with Jamf Insights (EU) has been restored. An issue with the credential rotation process prevented Jamf Insights from authenticating to customers' Jamf Pro instances. We apologize for any inconvenience. We will publish an analysis of this incident once we have completed our internal investigation. Customer Impact: Up to 900 EU tenants were affected. During the interruption, affected customers were unable to issue MDM commands or refresh device data (including extension attributes) through Jamf Insights.
Resolved
This incident has been resolved and we are seeing all platform functions operate normally.
Resolved
We did not experience any further issues after we put the fix in place.
Resolved
On June 8, 2026, between 08:40 UTC and 09:30 UTC, the Claude Opus 4.7 model experienced degraded availability with error rates peaking at 8.4% and averaging 1.9%. This was due to an upstream provider issue that caused temporary unavailability and rate limiting on secondary failover systems. Users selecting Auto or alternative models were unaffected. We are improving provider failover mechanisms and monitoring to prevent similar issues.
Resolved
Systems are fully operational
Resolved
This incident has been resolved.
Resolved
Authentication to EOS Game Services failed or timed out between 12:03pm and 12:10pm EDT
Resolved
This incident has been resolved.
Resolved
This incident is now resolved. Thank you for your patience and understanding.
Resolved
We've identified the problem and deployed a fix. You may need to refresh (⌘+R / CTRL+R) to get the latest changes.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Dear Valued Customer, We recently experienced call failures in the India region for the 911600 series numbers. After initial investigation, our carrier partner was notified, who took corrective action and the incident was resolved Incident Start Time: 15th June 2026, 11:15 IST Incident End Time: 15th June 2026, 11:45 IST If you have any questions or concerns regarding this incident, please contact Plivo Support. Support portal: https://support.plivo.com/hc/en-us
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved