Oct 7, 08:53 PDT
Investigating - We are aware that users are experiencing delayed sends and receives on Injective Network. Buys, Sells, and Fiat withdrawals/deposits are not affected. We are investigating this issue and will provide an update shortly. Rest assured, your funds are safe.
Oct 7, 17:28 UTC
Identified - We've identified the cause of errors loading usage data. The Admin API usage report has recovered, and fixes for the platform.claude.com Usage and Rate limits pages are in progress. The most recent 30 minutes of usage may be delayed. Core functionality is not affected.
Oct 7, 16:36 UTC
Update - We are continuing to work on elevated errors affecting usage data on the platform.claude.com Usage and Rate limits pages and the Admin API usage report. A mitigation for the Usage page and the Admin API usage report is rolling out; once it is in place, the most recent usage may take about 30 minutes to appear there. Core functionality is not affected.
Oct 7, 13:25 UTC
Investigating - We are investigating elevated errors affecting usage data on the platform.claude.com Usage page and the Admin API usage report. Core functionality is not affected. We will provide an update as soon as possible.
\n\n\t\n\t\n\t\n\t\n\t\n\t\n\tAs part of Fastly’s global network expansion, we will be adding a Mexico City (AZP) to Fastly's Mexico City network. \n\n
\nThis facility will initially launch as a limited availability deployment on the 7th of October 2026, meaning not all customer traffic will be routed through this new location during this initial phase.
Our estimated duration is 4h.
\nWhen this change is applied, customers may observe additional origin traffic as new cache nodes retrieve content from origin. Please verify that your origin access lists allow the full range of Fastly IP addresses Public IP List | Fastly Documentation.
Customers with any questions or concerns may engage with our Support team through Fastly Support or by contacting your designated account management team members.
\n\n\n\n
\n
Update - Tue, 06 Oct 2026 21:30:28 UTC
Zscaler is prioritizing the issue and is actively working to isolate the problem and identify the root cause. We appreciate your patience and understanding during this investigation. Additional updates will be provided as more information becomes available.
Oct 6, 21:43 UTC
Update - The F5 Distributed Cloud engineering team continues to make progress toward restoring the Melbourne (ME1) Regional Edge, and restoration efforts remain on track. Proactive monitoring is in place to help maintain service continuity across the region during this process.
We appreciate your patience and will provide further updates as restoration progresses.
Oct 5, 23:36 UTC
Identified - Our F5 Distributed Cloud engineering team continues to work on the restoration of the Melbourne (ME1) Regional Edge. Restoration activities remain on track, and additional updates will be provided as progress is made. The engineering team has enabled a proactive monitoring stage to ensure service continuity throughout the region. We will share further updates as more information becomes available.
Oct 5, 16:30 UTC
Update - We are currently investigating a hardware issue within our Melbourne region. Customer traffic continues to route normally over secondary paths.
Our network engineering team is actively working with hardware vendor support to complete diagnostic procedures.
We will share further updates as more information becomes available.
Oct 5, 15:46 UTC
Investigating - This advisory is to inform you that we are currently investigating reports of service degradation affecting Melbourne.
We understand this may be affecting your operations and we are committed to providing transparent and timely updates as more information becomes available. While we gather more information, we recommend monitoring the progress on this site (https://www.f5cloudstatus.com/) for the latest update.
Investigation Status:
•\tWe have identified potential service impact at 03:42 PM UTC
•\tOur incident response team has been fully mobilized;
•\tInitial investigation and impact assessment efforts are underway.
Next Steps:
•\tA detailed incident notification will be provided within 30 minutes;
•\tOur teams are working to determine the root cause of the incident;
•\tWe will share mitigation steps as soon as they become available.
We appreciate your patience as we work to resolve this situation. If you are experiencing a critical business impact, please contact our support team through your established channels.
Thank you for your continued support and trust in F5.
2026-09-22 19:23:17 UTC: Investigating
Cloudflare is investigating an issue where Cloudflare One Client customers are incorrectly challenged while visiting some websites.
2026-09-23 11:02:41 UTC: Identified
The issue has been identified and a fix is being implemented.
","link":"https://www.cloudflarestatus.com/incidents/tl0vrgjy99r0","pubDate":"2026-09-22T19:23:17.000Z","status":"identified","impact":"minor","isResolved":false,"created_at":"2026-09-22T19:23:17.000Z","resolved_at":null,"started_at":"2026-09-22T19:23:17.000Z","startTime":"2026-09-22T19:23:17.263Z","endTime":null,"updatedAt":"2026-09-23T11:02:41.000Z","monitoringAt":null,"vendor":"Cloudflare","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"cloudflare","_parsedIsResolved":false,"_parsedStartTime":"2026-09-22T19:23:17.000Z","_parsedEndTime":null},{"id":"tag:status.redhat.com,2005:Incident/31500616","title":"Support Cases - Post Upgrade Issues","description":" Sep 22, 17:52 UTC
Investigating - We are aware of ongoing issues when accessing support cases after our CRM upgrade. We are actively working to resolve them.
Try refreshing your browser first. If you still need help, contact us at techsupport@redhat.com or by phone with your Account and User Details, or view https://access.redhat.com/articles/7146730
\n\n\nFastly is announcing General Availability on September 29, 2026 of Controlled Support Access (CSA). CSA gives customers more control and visibility over Fastly employee access by requiring customer approval for Fastly write/enforcing access. Approved access is time-bound, auditable, and customer-revocable. Read-only troubleshooting remains available so Fastly can continue diagnosing issues efficiently.\n
\n
\n\t\tCSA is default OFF at General Availability (GA). Customers who want to enable CSA can opt in directly from the Fastly Control Panel.
What’s Changing?
\n\t\n\t\tTo learn more, see the \n\t\t\n\t\t\tControlled support access\n\t\t\n\t\t documentation.\n\t
\n\t\n\t\tThe documentation explains standard CSA requests/grants, customer approval and revocation, audit visibility, and Breakglass emergency access.\n\t
\n\t\n\t\tCSA is disabled by default at GA, meaning no action is required unless you wish to use it. Superusers can enable the feature directly within the Fastly Control Panel.\n\t
\n\t\n\t\tCustomers with any questions or concerns may engage with our Support team through \n\t\t\n\t\t\thttps://support.fastly.com\n\t\t\n\t\t or by contacting your designated account management team members.\n\t
\n\t Sep 19, 01:49 PDT
Investigating - We are aware that some users may experience delays in sends and receives on the MultiversX (EGLD) network due to a network issue. Buys, sells, and fiat withdrawals/deposits are not affected. Your funds are safe.
\n\tOn October 13, 2026, at 00:00 UTC, Fastly will publish additional public IP address ranges to our \n\t\n\t\tPublic IP List\n\t\n\t API endpoint. \n
\n\n\tTo prepare for future use, we recommend updating your IP prefix lists as soon as possible.\n
\n\n\tThe following IP block(s) will be added to our range list:\n
\n\n\t\t\tIPv4:\n\t\t\t\n\t\t\t\n\t\t\t90.98.0.0/17\n\t\t\t, \n\t\t\t90.98.128.0/18\n\t\t
\n\t\n\t\t\tIPv6:\n\t\t\t\n\t\t\t\n\t\t\t2a04:4e42::/31 \n\t\t\t(expanded from \n\t\t\t2a04:4e42::/32\n\t\t\t), \n\t\t\t2a04:4e44::/32\n\t\t
\n\t\n\tThe deployment of these new prefixes for active use is scheduled for January 11, 2027, at 00:00 UTC, and all currently published IP prefixes will remain unchanged. \n
\n\n\n\n
\n\n\tCustomers with any questions or concerns may engage with our Support team through \n\t\n\t\thttps://support.fastly.com\n\t\n\t or by contacting your designated Customer Success team members.\n
","pubDate":"2026-09-14T17:56:00.000Z","link":"https://www.fastlystatus.com/incident/378836","status":"unknown","impact":"none","isResolved":false,"created_at":"2026-09-14T17:56:00.000Z","resolved_at":null,"started_at":"2026-09-14T17:56:00.000Z","startTime":"2026-09-14T17:56:00.000Z","endTime":null,"updatedAt":"2026-09-14T17:56:00.000Z","guid":"fastly-incident-378836","vendor":"Fastly","healthScoreSeverity":"unknown","healthScoreSeveritySource":"unknown","vendorId":"fastly","_parsedIsResolved":true,"_parsedStartTime":"2026-09-14T17:56:00.000Z","_parsedEndTime":null},{"id":"20004430","incidentId":"20004430","title":"Spiff Salesforce Spiff Feature Degradation - SPIFF-US1","description":"Advanced Analytics data is stale as of 09/14/26 1:40 PM UTC","pubDate":"2026-09-14T13:40:00.000Z","link":"https://status.salesforce.com/incidents/20004430","status":"Active","impact":"minor","type":"Degradation","isResolved":false,"created_at":"2026-09-14T13:40:00.000Z","resolved_at":null,"startTime":"2026-09-14T13:40:00.000Z","endTime":null,"updatedAt":"2026-09-14T17:11:52.435Z","serviceKeys":["Spiff"],"instanceKeys":["SPIFF-US1"],"enhancedInstanceKeys":[{"key":"SPIFF-US1","location":"NA","city":null,"stateName":null,"stateCode":null,"countryName":null,"countryCode":null,"environment":"production","status":"OK","isActive":true,"releaseVersion":null,"maintenanceWindow":null}],"incidentImpacts":[{"id":20004761,"startTime":"2026-09-14T13:40:00.000Z","endTime":null,"type":"salesforceSpiffFeatureDegradation","severity":"minor","createdAt":"2026-09-14T17:11:08.945Z","updatedAt":"2026-09-14T17:11:52.430Z","startTimeCreatedAt":"2026-09-14T17:11:08.945Z","startTimeModifiedAt":"2026-09-14T17:11:52.431Z","endTimeCreatedAt":null,"endTimeModifiedAt":null}],"timeline":[{"title":"Degradation Started","content":"salesforceSpiffFeatureDegradation","createdAt":"2026-09-14T17:11:08.945Z","updatedAt":"2026-09-14T17:11:52.431Z","entryType":"impact_start","startTime":"2026-09-14T13:40:00.000Z","sourceId":20004761,"sourceType":"impact","impactStartTime":"2026-09-14T17:11:08.945Z"}],"guid":"20004430","vendor":"Salesforce","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"salesforce","_parsedIsResolved":true,"_parsedStartTime":"2026-09-14T13:40:00.000Z","_parsedEndTime":null},{"id":"zwqnwskcjw0h","title":"CRM Sync Delays","description":"Status: investigating\n\nWe are currently experiencing delays with CRM syncing for a subset of users. Some users may experience slower load times or delays with CRM sync. Our engineering team is actively working on a resolution and we will share an update as soon as we have more information.","pubDate":"2026-09-09T16:00:25.881-04:00","link":"https://stspg.io/hphtkz3v3vq9","status":"investigating","impact":"major","isResolved":false,"created_at":"2026-09-09T16:00:25.812-04:00","resolved_at":null,"started_at":"2026-09-09T16:00:25.812-04:00","startTime":"2026-09-09T16:00:25.812-04:00","endTime":null,"updatedAt":"2026-09-09T16:00:25.881-04:00","guid":"zwqnwskcjw0h","vendor":"Salesloft","healthScoreSeverity":"major","healthScoreSeveritySource":"impact","vendorId":"salesloft","_parsedIsResolved":false,"_parsedStartTime":"2026-09-09T20:00:25.812Z","_parsedEndTime":null},{"id":"mcv3ht4pcdsk","title":"Strata Logging Service : Email Log Forwarding Service Disruption","description":"Status: investigating\n\nStatus: Investigating
Severity: Degraded
Locations: Berlin, Council Bluffs, Doha, Eemshaven, Frankfurt, Hong Kong, Johannesburg, London, Madrid, Milan, Montreal, Osaka, Paris, Riyadh, Seoul, Singapore, Sydney, São Paulo, Taipei, Tel Aviv, Warsaw, Zurich
Impact:
Email log forwarding service is currently experiencing issues causing delayed or undelivered emails. We are actively resolving them. We will post additional information when available.
Workaround:
None
An incident has been identified. We are actively investigating to restore services.
","pubDate":"2026-09-03T19:56:10.586Z","link":"https://stspg.io/qf5njfcj3y6t","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-09-03T19:56:10.586Z","resolved_at":null,"startTime":"2026-09-03T19:56:10.586Z","endTime":null,"updatedAt":"2026-09-09T17:43:24.550Z","guid":"mcv3ht4pcdsk","_source":"api-v2","vendor":"Palo Alto","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"paloalto","_parsedIsResolved":false,"_parsedStartTime":"2026-09-03T19:56:10.586Z","_parsedEndTime":null},{"id":"fastly-incident-378764","title":"St. Louis (STL) Rerouted Traffic","description":"Traffic in St. Louis (STL) has been temporarily rerouted.
All other locations and services are unaffected.
2026-08-27 18:46:19 UTC: Investigating
Cloudflare is investigating issues with Cloudflare WARP and Cloudflare Zero Trust users being incorrectly geolocated by some third party services.
2026-08-27 18:56:11 UTC: Identified
The issue has been identified and we are working with third party providers to fix it.
2026-08-28 00:55:12 UTC: Identified
We are continuing to work on a fix for this issue.
2026-08-28 11:30:28 UTC: Identified
We are continuing to work on a fix for this issue.
2026-08-29 15:31:17 UTC: Identified
We are continuing to work on a fix for this issue.
2026-08-30 15:51:03 UTC: Identified
We are continuing to work on a fix for this issue.
2026-08-31 15:15:03 UTC: Identified
We are continuing to work on a fix for this issue.
2026-09-01 08:29:56 UTC: Identified
We are continuing to work on a fix for this issue.
","link":"https://www.cloudflarestatus.com/incidents/9g65dxfbcjln","pubDate":"2026-08-27T18:46:19.000Z","status":"identified","impact":"minor","isResolved":false,"created_at":"2026-08-27T18:46:19.000Z","resolved_at":null,"started_at":"2026-08-27T18:46:19.000Z","startTime":"2026-08-27T18:46:19.023Z","endTime":null,"updatedAt":"2026-09-01T08:29:56.000Z","monitoringAt":null,"vendor":"Cloudflare","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"cloudflare","_parsedIsResolved":false,"_parsedStartTime":"2026-08-27T18:46:19.000Z","_parsedEndTime":null},{"title":"ZDX Administration UI Issue","link":"https://trust.zscaler.us/zdxgov.net/posts/12996","description":"Zscaler has detected an issue with its zdxgov.net (FedRAMP Moderate), zdxten.net (FedRAMP High) Cloud.We are investigating an issue causing Next-Gen Waf (NGWAF) dashboard to display blank or missing performance data for some customers. This is a visible issue only - NGWAF protection and services are no impacted. Our engineers are actively working to diagnose the contributing factor. We will provide another update as more information becomes available or within the hour
All other products and services are unaffected by this incident
","pubDate":"2026-08-24T15:16:00.000Z","link":"https://www.fastlystatus.com/incident/378740","status":"investigating","impact":"none","isResolved":false,"created_at":"2026-08-24T15:16:00.000Z","resolved_at":null,"started_at":"2026-08-24T15:16:00.000Z","startTime":"2026-08-24T15:16:00.000Z","endTime":null,"updatedAt":"2026-08-24T15:16:00.000Z","guid":"fastly-incident-378740","vendor":"Fastly","healthScoreSeverity":"minor","healthScoreSeveritySource":"text","vendorId":"fastly","_parsedIsResolved":false,"_parsedStartTime":"2026-08-24T15:16:00.000Z","_parsedEndTime":null},{"id":"https://status.cloud.solarwinds.com/incidents/fc6p0l3hl875","title":"Delayed Data Ingestion [EU-01]","description":"The backfill is now complete. All data has been restored. New data is now processing normally, and alerts and dashboards should reflect up-to-date information.","pubDate":"2026-08-21T00:41:55.969Z","link":"https://stspg.io/9gzmd3m33gv6","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-08-21T00:41:55.969Z","resolved_at":null,"started_at":"2026-08-21T00:41:55.969Z","startTime":"2026-08-21T00:41:55.969Z","endTime":null,"updatedAt":"2026-08-21T00:41:55.969Z","affectedRegions":"EU-01","maintenanceEndDate":null,"vendor":"SolarWinds","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"solarwinds","_parsedIsResolved":false,"_parsedStartTime":"2026-08-21T00:41:55.969Z","_parsedEndTime":null},{"id":"https://www.stripestatus.com/incidents/y8898n2yk19y","title":"Elevated API errors","description":"From 12:04 to 12:26 UTC on August 1st, we saw elevated error rates and response times with the Stripe API. The issue is resolved and we will continue to monitor.","pubDate":"2026-08-01T12:45:48.696Z","link":"https://stspg.io/sbldmtv3y0jq","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-08-01T12:45:48.696Z","resolved_at":null,"startTime":"2026-08-01T12:45:48.696Z","endTime":null,"updatedAt":"2026-08-01T12:45:48.696Z","vendor":"Stripe","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"stripe","_parsedIsResolved":false,"_parsedStartTime":"2026-08-01T12:45:48.696Z","_parsedEndTime":null},{"id":"https://www.stripestatus.com/incidents/hcmr28nnd39l","title":"Elevated API errors","description":"From 23:55 July 31st - 00:17 August 1st UTC, we saw elevated error rates and response times with the API. We are now seeing recovery and will continue monitoring.","pubDate":"2026-08-01T00:50:40.148Z","link":"https://stspg.io/l0fsvp40d3hy","status":"investigating","impact":"minor","isResolved":false,"created_at":"2026-08-01T00:50:40.148Z","resolved_at":null,"startTime":"2026-08-01T00:50:40.148Z","endTime":null,"updatedAt":"2026-08-01T00:50:40.148Z","vendor":"Stripe","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"stripe","_parsedIsResolved":false,"_parsedStartTime":"2026-08-01T00:50:40.148Z","_parsedEndTime":null},{"id":"fastly-incident-378683","title":"Port Blair (IXZ) Rerouted Traffic","description":"Traffic in Port Blair (IXZ) has been temporarily rerouted.
All other locations and services are unaffected.
Mar 4, 04:55 UTC
Update - AWS continues to make progress on recovery efforts across multiple workstreams. From now on, updates will be delivered directly to affected customers through the AWS Personal Health Dashboard. Customers who require assistance with this event are encouraged to contact AWS Support through the AWS Management Console or the AWS Support Center.
AWS Status Page: https://health.aws.amazon.com/health/status
Mar 3, 10:21 UTC
Update - The outage is still ongoing on AWS side. The AWS Management Console is now operational, and AWS is recommending to retry operations where possible, although most of the underlying service are still offline.
Mar 2, 17:52 UTC
Update - ROSA clusters deployed in me-central-1 are degraded due to availability zone outages. We recommend customers enact their disaster recovery plans and recover from remote backups into alternate AWS Regions, ideally in Europe. Please refer to AWS Health for more information and recommendations on workload relocation.
Mar 2, 13:37 UTC
Update - Availability Zones in the ME-CENTRAL-1 Region (mec1-az2, mec1-az3) have been impacted by a power outage. Customers are advised to schedule their workloads into another availability zone.
Mar 1, 14:26 UTC
Update - An Availability Zone in the ME-CENTRAL-1 Region (mec1-az2) has been impacted by a power outage. Customers are advised to schedule their workloads into another availability zone.
Mar 1, 14:02 UTC
Identified - ROSA clusters degraded in me-central
AWS Status Page: https://health.aws.amazon.com/health/status
Mar 4, 04:44 UTC
Update - The outage is still ongoing on the AWS side, and recovery efforts are ongoing. AWS is recommending customers launch replacement resources in one of the unaffected Availability Zones or an alternate AWS Region
Mar 2, 17:52 UTC
Update - ROSA clusters deployed in me-south-1 are degraded due to availability zone outages. We recommend customers enact their disaster recovery plans and recover from remote backups into alternate AWS Regions, ideally in Europe. Please refer to AWS Health for more information and recommendations on workload relocation.
Mar 2, 07:22 UTC
Identified - ROSA clusters degraded in me-south due to a localized power issue in mes1-az2.
Customers are advised to schedule their workloads into another availability zone.
AWS Status Page: https://health.aws.amazon.com/health/status
Update - Wed, 07 Oct 2026 17:04:58 UTC
We have identified the root cause of the issue and working on resolution.
Status: Investigating
Severity: Degraded
Locations: Seoul, Singapore, Sydney
Impact:
Users in the affected regions will experience latency/lag while viewing SLS logs in SCM logviewer. No impact to SLS ingestion
Workaround:
NA
An incident has been identified. We are actively investigating to restore services.
","pubDate":"2026-10-07T07:27:11.673Z","link":"https://stspg.io/2mmx7pcflcpw","status":"monitoring","impact":"minor","isResolved":false,"created_at":"2026-10-07T07:27:11.673Z","resolved_at":null,"startTime":"2026-10-07T07:27:11.673Z","endTime":null,"updatedAt":"2026-10-07T16:01:42.084Z","guid":"8sl1n8b7h0y9","_source":"api-v2","vendor":"Palo Alto","healthScoreSeverity":"minor","healthScoreSeveritySource":"impact","vendorId":"paloalto","_parsedIsResolved":false,"_parsedStartTime":"2026-10-07T07:27:11.673Z","_parsedEndTime":null},{"title":"ZCC Flow Logging Issue","link":"https://trust.zscaler.com/zscaler.net/posts/32216","description":"Update - Wed, 07 Oct 2026 11:15:48 UTC
We have identified the root cause of the issue and working on resolution.
Jul 23, 8:57 PM UTC
INVESTIGATING -
Chat (/api/v1/chat/completions) cannot be reached by our automated monitoring.
\n","pubDate":"2026-07-23T20:57:54.000Z","link":"status.openrouter.ai/incidents/YGz9Og5Qm8vO","status":"monitoring","impact":"none","isResolved":false,"created_at":"2026-07-23T20:57:00.000Z","resolved_at":null,"started_at":"2026-07-23T20:57:00.000Z","startTime":"2026-07-23T20:57:00.000Z","endTime":null,"updatedAt":"2026-07-23T20:57:54.000Z","guid":"status.openrouter.ai/incidents/YGz9Og5Qm8vO","vendor":"OpenRouter.ai","healthScoreSeverity":"unknown","healthScoreSeveritySource":"unknown","vendorId":"openrouter","_parsedIsResolved":false,"_parsedStartTime":"2026-07-23T20:57:00.000Z","_parsedEndTime":null},{"id":"https://bitbucket.status.atlassian.com/incidents/fxr44q252yzj","incidentId":"https://bitbucket.status.atlassian.com/incidents/fxr44q252yzj","title":"Atlassian Login Issues - Global Users","description":"Apr 13, 07:29 UTC
Monitoring - Our team is aware that some users were unable to log in to Atlassian products with their Atlassian accounts. While we believe this issue is now resolved, we are continuing to monitor all products and services for any ongoing impact.
Our team is investigating with urgency, and we will provide an update within 1 hour.
Mar 3, 16:45 UTC
Identified - The issue has been identified and a fix is being implemented.
Mar 3, 16:42 UTC
Investigating - We are currently investigating this issue.