May 13, 06:22 UTC
Investigating - Catchpoint Last Mile node LM - Pondicherry, IN - BSNL will not run tests due to an issue at Last Mile site.
We will update the status as soon as there is additional information available.
We’re investigating this issue:
We'll continue to provide updates every 30 minutes until the impact is resolved for all users.
We’re investigating this issue:
We'll continue to provide updates every 30 minutes until the impact is resolved for all users.
May 7, 15:44 UTC
Investigating - Catchpoint Last Mile node LM - Suwanee, US - AT&T will not run tests due to an issue at Last Mile site.
We will update the status as soon as there is additional information available.
Mar 27, 03:09 PDT
Update - We are investigating reports of intermittent TCP connectivity issues affecting inbound and outbound SMPP connections within our IE1 region. This issue is currently impacting a subset of customers utilizing SMPP for messaging traffic through this specific gateway. We are actively working to resolve the issue. We expect to provide another update in 2 hours or as soon as more information becomes available.
Mar 27, 02:09 PDT
Update - We are investigating reports of intermittent TCP connectivity issues affecting inbound and outbound SMPP connections within our IE1 region. This issue is currently impacting a subset of customers utilizing SMPP for messaging traffic through this specific gateway. We are actively working to resolve the issue. We expect to provide another update in 1 hour or as soon as more information becomes available.
Mar 27, 01:58 PDT
Investigating - Our monitoring systems have detected a potential issue with Programmable Messaging. Our engineers have been alerted and are investigating. We will provide an update when we have more details.
Mar 11, 16:12 PDT
Investigating - Twilio customers may be experiencing User Authentication Identity API errors for XL Axiata in Indonesia. Our team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available.
May 13, 10:12 UTC
Update - We are continuing to monitor for any further issues.
May 13, 06:15 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
May 13, 03:50 UTC
Identified - The issue has been identified and a fix is being implemented.
May 13, 03:37 UTC
Update - The team continues to investigate the issue. Work is ongoing to identify the root cause and restore the service. We will provide further updates as soon as more information becomes available.
May 12, 19:16 UTC
Investigating - A network issue has been identified at Plano PoP and is currently being investigated. Traffic has been automatically re-routed to other PoPs.
If you have any questions regarding this incident, please contact FortiCare Support https://www.fortinet.com/support/contact and reference FortiSASE Operations ticket #490164.
Update - Tue, 12 May 2026 19:28:21 UTC
Zscaler continues to investigate the issue and work toward identifying appropriate mitigation steps. Additional updates will be provided as more information becomes available.
Update - Tue, 12 May 2026 20:18:16 UTC
Zscaler has identified the cause of the issue and is actively developing and validating a mitigation fix. Multiple validation steps are being performed to ensure service stability and effectiveness prior to deployment. Additional updates will be provided as progress continues.
Update - Wed, 13 May 2026 08:15:19 UTC
Zscaler is continuing to perform rigorous validation and testing of the identified mitigation fix. These comprehensive validation steps are being conducted to ensure service stability and effectiveness across all environments prior to deployment. We will provide a further update once the fix is ready for rollout.
Update - Tue, 12 May 2026 19:28:21 UTC
Zscaler continues to investigate the issue and work toward identifying appropriate mitigation steps. Additional updates will be provided as more information becomes available.
Update - Tue, 12 May 2026 20:18:16 UTC
Zscaler has identified the cause of the issue and is actively developing and validating a mitigation fix. Multiple validation steps are being performed to ensure service stability and effectiveness prior to deployment. Additional updates will be provided as progress continues.
Update - Wed, 13 May 2026 08:15:19 UTC
Zscaler is continuing to perform rigorous validation and testing of the identified mitigation fix. These comprehensive validation steps are being conducted to ensure service stability and effectiveness across all environments prior to deployment. We will provide a further update once the fix is ready for rollout.
May 6, 21:43 UTC
Monitoring -
Status: Monitoring
Severity: Disruption
Locations: Council Bluffs, Montreal, Toronto
Impact:
Command Center and Visibility dashboards are currently impacted. API responses for these dashboards may be degraded or slower than usual. We are actively working on mitigation and will provide updates as we make progress.
Workaround:
None
A fix has been implemented. We are actively monitoring to ensure full restoration of services.
May 6, 13:46 UTC
Investigating -
Status: Investigating
Severity: Disruption
Locations: Council Bluffs, Montreal, Toronto
Impact:
Command Center and Visibility dashboards are currently impacted. API responses for these dashboards may be degraded or slower than usual. We are actively working on mitigation and will provide updates as we make progress.
Workaround:
None
An incident has been identified. We are actively investigating to restore services.
","pubDate":"Wed, 06 May 2026 21:43:55 +0000","link":"https://sase-secondary.status.paloaltonetworks.com/incidents/2zg9nkkn8pxd","status":"monitoring","impact":"none","isResolved":false,"created_at":"Wed, 06 May 2026 21:43:55 +0000","resolved_at":null,"startTime":"Wed, 06 May 2026 21:43:55 +0000","endTime":null,"updatedAt":"Wed, 06 May 2026 21:43:55 +0000","affectedComponents":[],"incidentUpdates":[],"guid":"https://sase-secondary.status.paloaltonetworks.com/incidents/2zg9nkkn8pxd","_source":"api-v2","vendor":"Palo Alto","vendorId":"paloalto","_parsedIsResolved":false,"_parsedStartTime":"2026-05-06T21:43:55.000Z","_parsedEndTime":null},{"id":"xlh20wf0hd70","title":"Bot Management Issues","description":"2026-05-05 08:04:42 UTC: Investigating
Cloudflare is investigating issues with our Bot Management feature. Customers may experience an unexpected increase in Bot Management rules matching detection IDs 50331648 and 50331649.
We are working to mitigate this problem. More updates to follow shortly.
2026-05-05 09:17:42 UTC: Identified
The issue has been identified and a fix is being implemented.
2026-05-05 15:59:59 UTC: Identified
We have identified an issue with our Bot Management feature causing rules with IDs 50331648 and 50331649 to match traffic unexpectedly. Customers using Bot Management may have seen an increase in requests flagged by these rules. We have disabled the affected feature to prevent further impact. Our team is actively working on a fix.
2026-05-06 09:39:51 UTC: Identified
We have identified an issue with our Bot Management feature causing rules with IDs 50331648 and 50331649 to match traffic unexpectedly from April 1st 2026. Some customers using Bot Management may have seen an increase in requests flagged by these rules. We have disabled the affected feature to prevent further impact. A fix has been implemented, it will take 48 hours for detections to stabilize.
2026-05-09 00:39:29 UTC: Identified
We are continuing to update the identified issues with our Bot Management features for the rule IDs: 50331648, 50331649. We have disabled the affected feature globally to prevent further impact. An additional 72 hours is needed for stabilization, and review of the detections.
2026-05-11 15:49:54 UTC: Identified
We are continuing to update the identified issues with our Bot Management features for the rule IDs: 50331648, 50331649. After a additional review we determined that impact existed prior April 1st 2026, and was present for a subset of Bot Management Customers. We have disabled the affected feature globally to prevent further impact. An additional 72 hours is needed for stabilization, and review the detections.
","pubDate":"2026-05-05T08:04:41.960Z","link":"https://stspg.io/hx27fxg9f6h6","status":"identified","impact":"minor","isResolved":false,"created_at":"2026-05-05T08:04:41.960Z","resolved_at":null,"started_at":"2026-05-06T09:39:51.000Z","startTime":"2026-05-05T08:04:41.951Z","endTime":null,"updatedAt":"2026-05-11T15:49:54.588Z","incidentUpdates":[{"id":"d9xv22bnq989","status":"identified","body":"We are continuing to update the identified issues with our Bot Management features for the rule IDs: 50331648, 50331649. After a additional review we determined that impact existed prior April 1st 2026, and was present for a subset of Bot Management Customers. We have disabled the affected feature globally to prevent further impact. An additional 72 hours is needed for stabilization, and review the detections.","incident_id":"xlh20wf0hd70","created_at":"2026-05-11T15:49:54.585Z","updated_at":"2026-05-11T15:49:54.585Z","display_at":"2026-05-11T15:49:54.585Z","affected_components":[{"code":"s0991jwsqllx","name":"Cloudflare Sites and Services - Bot Management","old_status":"degraded_performance","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null},{"id":"9rzw93mmdjzx","status":"identified","body":"We are continuing to update the identified issues with our Bot Management features for the rule IDs: 50331648, 50331649. We have disabled the affected feature globally to prevent further impact. An additional 72 hours is needed for stabilization, and review of the detections.","incident_id":"xlh20wf0hd70","created_at":"2026-05-09T00:39:29.242Z","updated_at":"2026-05-09T00:39:29.242Z","display_at":"2026-05-09T00:39:29.242Z","affected_components":[{"code":"s0991jwsqllx","name":"Cloudflare Sites and Services - Bot Management","old_status":"degraded_performance","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null},{"id":"q426x3wljlw3","status":"identified","body":"We have identified an issue with our Bot Management feature causing rules with IDs 50331648 and 50331649 to match traffic unexpectedly from April 1st 2026. Some customers using Bot Management may have seen an increase in requests flagged by these rules. We have disabled the affected feature to prevent further impact. A fix has been implemented, it will take 48 hours for detections to stabilize.","incident_id":"xlh20wf0hd70","created_at":"2026-05-06T09:39:51.582Z","updated_at":"2026-05-06T11:26:20.502Z","display_at":"2026-05-06T09:39:51.000Z","affected_components":[{"code":"s0991jwsqllx","name":"Cloudflare Sites and Services - Bot Management","old_status":"degraded_performance","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null},{"id":"1xv3t2splz7b","status":"identified","body":"We have identified an issue with our Bot Management feature causing rules with IDs 50331648 and 50331649 to match traffic unexpectedly. Customers using Bot Management may have seen an increase in requests flagged by these rules. We have disabled the affected feature to prevent further impact. Our team is actively working on a fix.","incident_id":"xlh20wf0hd70","created_at":"2026-05-05T15:59:59.518Z","updated_at":"2026-05-05T15:59:59.518Z","display_at":"2026-05-05T15:59:59.518Z","affected_components":[{"code":"s0991jwsqllx","name":"Cloudflare Sites and Services - Bot Management","old_status":"degraded_performance","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null},{"id":"phm1kqkqypz0","status":"identified","body":"The issue has been identified and a fix is being implemented.","incident_id":"xlh20wf0hd70","created_at":"2026-05-05T09:17:42.484Z","updated_at":"2026-05-05T09:17:42.484Z","display_at":"2026-05-05T09:17:42.484Z","affected_components":[{"code":"s0991jwsqllx","name":"Cloudflare Sites and Services - Bot Management","old_status":"degraded_performance","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null},{"id":"nkm2815q1735","status":"investigating","body":"Cloudflare is investigating issues with our Bot Management feature. Customers may experience an unexpected increase in Bot Management rules matching detection IDs 50331648 and 50331649.\n\nWe are working to mitigate this problem. More updates to follow shortly.","incident_id":"xlh20wf0hd70","created_at":"2026-05-05T08:04:42.052Z","updated_at":"2026-05-05T08:04:42.052Z","display_at":"2026-05-05T08:04:42.052Z","affected_components":[{"code":"s0991jwsqllx","name":"Cloudflare Sites and Services - Bot Management","old_status":"operational","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null}],"monitoringAt":null,"firstSeen":"2026-05-05T08:05:00.573Z","lastUpdated":"2026-05-11T15:50:00.394Z","vendor":"Cloudflare","vendorId":"cloudflare","_parsedIsResolved":false,"_parsedStartTime":"2026-05-06T09:39:51.000Z","_parsedEndTime":null},{"id":"gnnqg2ww6gkx","title":"Barracuda Appliance Control : Configuration Backup to Cloud – Service Disruption","description":"Status: investigating\n\nWe are currently investigating this issue.","pubDate":"2026-04-23T09:15:44.500Z","link":"https://stspg.io/4brdpjr7ktn5","status":"monitoring","impact":"minor","isResolved":false,"created_at":"2026-04-23T09:15:44.494Z","resolved_at":null,"started_at":"2026-04-23T09:15:44.494Z","startTime":"2026-04-23T09:15:44.494Z","endTime":null,"updatedAt":"2026-04-23T09:31:19.740Z","incidentUpdates":[],"affectedComponents":[{"id":"49lgd3zs7wbg","name":"Cloud backups","status":"degraded_performance","created_at":"2017-07-06T20:50:26.571Z","updated_at":"2026-04-23T09:15:44.525Z","position":3,"description":"Some customers may be experiencing issues with cloud backups failing due to the error: \"File upload failed.\" We have implemented changes and are currently monitoring the situation. Our team is actively working to ensure the issue is fully resolved.","showcase":false,"start_date":null,"group_id":"p5z9pc1fpmtf","page_id":"k481728pjqn6","group":false,"only_show_if_degraded":false}],"guid":"gnnqg2ww6gkx","originalData":{"id":"gnnqg2ww6gkx","name":"Barracuda Appliance Control : Configuration Backup to Cloud – Service Disruption","status":"monitoring","created_at":"2026-04-23T09:15:44.500Z","updated_at":"2026-04-23T09:31:19.740Z","monitoring_at":"2026-04-23T09:31:19.710Z","resolved_at":null,"impact":"minor","shortlink":"https://stspg.io/4brdpjr7ktn5","started_at":"2026-04-23T09:15:44.494Z","page_id":"k481728pjqn6","incident_updates":"[Circular Reference]","components":"[Circular Reference]","reminder_intervals":null},"source":"api","vendor":"Barracuda Networks","vendorId":"barracuda","_parsedIsResolved":false,"_parsedStartTime":"2026-04-23T09:15:44.494Z","_parsedEndTime":null},{"id":"tag:status.redhat.com,2005:Incident/28729618","title":"AWS Outage: me-central","description":"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
May 13, 10:12 UTC
Update - We are continuing to monitor for any further issues.
May 13, 06:15 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
May 13, 03:50 UTC
Identified - The issue has been identified and a fix is being implemented.
May 13, 03:37 UTC
Update - The team continues to investigate the issue. Work is ongoing to identify the root cause and restore the service. We will provide further updates as soon as more information becomes available.
May 12, 19:16 UTC
Investigating - A network issue has been identified at Plano PoP and is currently being investigated. Traffic has been automatically re-routed to other PoPs.
If you have any questions regarding this incident, please contact FortiCare Support https://www.fortinet.com/support/contact and reference FortiSASE Operations ticket #490164.
Update - Tue, 12 May 2026 19:28:21 UTC
Zscaler continues to investigate the issue and work toward identifying appropriate mitigation steps. Additional updates will be provided as more information becomes available.
Update - Tue, 12 May 2026 20:18:16 UTC
Zscaler has identified the cause of the issue and is actively developing and validating a mitigation fix. Multiple validation steps are being performed to ensure service stability and effectiveness prior to deployment. Additional updates will be provided as progress continues.
Update - Wed, 13 May 2026 08:15:19 UTC
Zscaler is continuing to perform rigorous validation and testing of the identified mitigation fix. These comprehensive validation steps are being conducted to ensure service stability and effectiveness across all environments prior to deployment. We will provide a further update once the fix is ready for rollout.
Update - Tue, 12 May 2026 19:28:21 UTC
Zscaler continues to investigate the issue and work toward identifying appropriate mitigation steps. Additional updates will be provided as more information becomes available.
Update - Tue, 12 May 2026 20:18:16 UTC
Zscaler has identified the cause of the issue and is actively developing and validating a mitigation fix. Multiple validation steps are being performed to ensure service stability and effectiveness prior to deployment. Additional updates will be provided as progress continues.
Update - Wed, 13 May 2026 08:15:19 UTC
Zscaler is continuing to perform rigorous validation and testing of the identified mitigation fix. These comprehensive validation steps are being conducted to ensure service stability and effectiveness across all environments prior to deployment. We will provide a further update once the fix is ready for rollout.
May 6, 21:43 UTC
Monitoring -
Status: Monitoring
Severity: Disruption
Locations: Council Bluffs, Montreal, Toronto
Impact:
Command Center and Visibility dashboards are currently impacted. API responses for these dashboards may be degraded or slower than usual. We are actively working on mitigation and will provide updates as we make progress.
Workaround:
None
A fix has been implemented. We are actively monitoring to ensure full restoration of services.
May 6, 13:46 UTC
Investigating -
Status: Investigating
Severity: Disruption
Locations: Council Bluffs, Montreal, Toronto
Impact:
Command Center and Visibility dashboards are currently impacted. API responses for these dashboards may be degraded or slower than usual. We are actively working on mitigation and will provide updates as we make progress.
Workaround:
None
An incident has been identified. We are actively investigating to restore services.
","pubDate":"Wed, 06 May 2026 21:43:55 +0000","link":"https://sase-secondary.status.paloaltonetworks.com/incidents/2zg9nkkn8pxd","status":"monitoring","impact":"none","isResolved":false,"created_at":"Wed, 06 May 2026 21:43:55 +0000","resolved_at":null,"startTime":"Wed, 06 May 2026 21:43:55 +0000","endTime":null,"updatedAt":"Wed, 06 May 2026 21:43:55 +0000","affectedComponents":[],"incidentUpdates":[],"guid":"https://sase-secondary.status.paloaltonetworks.com/incidents/2zg9nkkn8pxd","_source":"api-v2","vendor":"Palo Alto","vendorId":"paloalto","_parsedIsResolved":false,"_parsedStartTime":"2026-05-06T21:43:55.000Z","_parsedEndTime":null},{"id":"xlh20wf0hd70","title":"Bot Management Issues","description":"2026-05-05 08:04:42 UTC: Investigating
Cloudflare is investigating issues with our Bot Management feature. Customers may experience an unexpected increase in Bot Management rules matching detection IDs 50331648 and 50331649.
We are working to mitigate this problem. More updates to follow shortly.
2026-05-05 09:17:42 UTC: Identified
The issue has been identified and a fix is being implemented.
2026-05-05 15:59:59 UTC: Identified
We have identified an issue with our Bot Management feature causing rules with IDs 50331648 and 50331649 to match traffic unexpectedly. Customers using Bot Management may have seen an increase in requests flagged by these rules. We have disabled the affected feature to prevent further impact. Our team is actively working on a fix.
2026-05-06 09:39:51 UTC: Identified
We have identified an issue with our Bot Management feature causing rules with IDs 50331648 and 50331649 to match traffic unexpectedly from April 1st 2026. Some customers using Bot Management may have seen an increase in requests flagged by these rules. We have disabled the affected feature to prevent further impact. A fix has been implemented, it will take 48 hours for detections to stabilize.
2026-05-09 00:39:29 UTC: Identified
We are continuing to update the identified issues with our Bot Management features for the rule IDs: 50331648, 50331649. We have disabled the affected feature globally to prevent further impact. An additional 72 hours is needed for stabilization, and review of the detections.
2026-05-11 15:49:54 UTC: Identified
We are continuing to update the identified issues with our Bot Management features for the rule IDs: 50331648, 50331649. After a additional review we determined that impact existed prior April 1st 2026, and was present for a subset of Bot Management Customers. We have disabled the affected feature globally to prevent further impact. An additional 72 hours is needed for stabilization, and review the detections.
","pubDate":"2026-05-05T08:04:41.960Z","link":"https://stspg.io/hx27fxg9f6h6","status":"identified","impact":"minor","isResolved":false,"created_at":"2026-05-05T08:04:41.960Z","resolved_at":null,"started_at":"2026-05-06T09:39:51.000Z","startTime":"2026-05-05T08:04:41.951Z","endTime":null,"updatedAt":"2026-05-11T15:49:54.588Z","incidentUpdates":[{"id":"d9xv22bnq989","status":"identified","body":"We are continuing to update the identified issues with our Bot Management features for the rule IDs: 50331648, 50331649. After a additional review we determined that impact existed prior April 1st 2026, and was present for a subset of Bot Management Customers. We have disabled the affected feature globally to prevent further impact. An additional 72 hours is needed for stabilization, and review the detections.","incident_id":"xlh20wf0hd70","created_at":"2026-05-11T15:49:54.585Z","updated_at":"2026-05-11T15:49:54.585Z","display_at":"2026-05-11T15:49:54.585Z","affected_components":[{"code":"s0991jwsqllx","name":"Cloudflare Sites and Services - Bot Management","old_status":"degraded_performance","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null},{"id":"9rzw93mmdjzx","status":"identified","body":"We are continuing to update the identified issues with our Bot Management features for the rule IDs: 50331648, 50331649. We have disabled the affected feature globally to prevent further impact. An additional 72 hours is needed for stabilization, and review of the detections.","incident_id":"xlh20wf0hd70","created_at":"2026-05-09T00:39:29.242Z","updated_at":"2026-05-09T00:39:29.242Z","display_at":"2026-05-09T00:39:29.242Z","affected_components":[{"code":"s0991jwsqllx","name":"Cloudflare Sites and Services - Bot Management","old_status":"degraded_performance","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null},{"id":"q426x3wljlw3","status":"identified","body":"We have identified an issue with our Bot Management feature causing rules with IDs 50331648 and 50331649 to match traffic unexpectedly from April 1st 2026. Some customers using Bot Management may have seen an increase in requests flagged by these rules. We have disabled the affected feature to prevent further impact. A fix has been implemented, it will take 48 hours for detections to stabilize.","incident_id":"xlh20wf0hd70","created_at":"2026-05-06T09:39:51.582Z","updated_at":"2026-05-06T11:26:20.502Z","display_at":"2026-05-06T09:39:51.000Z","affected_components":[{"code":"s0991jwsqllx","name":"Cloudflare Sites and Services - Bot Management","old_status":"degraded_performance","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null},{"id":"1xv3t2splz7b","status":"identified","body":"We have identified an issue with our Bot Management feature causing rules with IDs 50331648 and 50331649 to match traffic unexpectedly. Customers using Bot Management may have seen an increase in requests flagged by these rules. We have disabled the affected feature to prevent further impact. Our team is actively working on a fix.","incident_id":"xlh20wf0hd70","created_at":"2026-05-05T15:59:59.518Z","updated_at":"2026-05-05T15:59:59.518Z","display_at":"2026-05-05T15:59:59.518Z","affected_components":[{"code":"s0991jwsqllx","name":"Cloudflare Sites and Services - Bot Management","old_status":"degraded_performance","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null},{"id":"phm1kqkqypz0","status":"identified","body":"The issue has been identified and a fix is being implemented.","incident_id":"xlh20wf0hd70","created_at":"2026-05-05T09:17:42.484Z","updated_at":"2026-05-05T09:17:42.484Z","display_at":"2026-05-05T09:17:42.484Z","affected_components":[{"code":"s0991jwsqllx","name":"Cloudflare Sites and Services - Bot Management","old_status":"degraded_performance","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null},{"id":"nkm2815q1735","status":"investigating","body":"Cloudflare is investigating issues with our Bot Management feature. Customers may experience an unexpected increase in Bot Management rules matching detection IDs 50331648 and 50331649.\n\nWe are working to mitigate this problem. More updates to follow shortly.","incident_id":"xlh20wf0hd70","created_at":"2026-05-05T08:04:42.052Z","updated_at":"2026-05-05T08:04:42.052Z","display_at":"2026-05-05T08:04:42.052Z","affected_components":[{"code":"s0991jwsqllx","name":"Cloudflare Sites and Services - Bot Management","old_status":"operational","new_status":"degraded_performance"}],"deliver_notifications":true,"custom_tweet":null,"tweet_id":null}],"monitoringAt":null,"firstSeen":"2026-05-05T08:05:00.573Z","lastUpdated":"2026-05-11T15:50:00.394Z","vendor":"Cloudflare","vendorId":"cloudflare","_parsedIsResolved":false,"_parsedStartTime":"2026-05-06T09:39:51.000Z","_parsedEndTime":null},{"id":"gnnqg2ww6gkx","title":"Barracuda Appliance Control : Configuration Backup to Cloud – Service Disruption","description":"Status: investigating\n\nWe are currently investigating this issue.","pubDate":"2026-04-23T09:15:44.500Z","link":"https://stspg.io/4brdpjr7ktn5","status":"monitoring","impact":"minor","isResolved":false,"created_at":"2026-04-23T09:15:44.494Z","resolved_at":null,"started_at":"2026-04-23T09:15:44.494Z","startTime":"2026-04-23T09:15:44.494Z","endTime":null,"updatedAt":"2026-04-23T09:31:19.740Z","incidentUpdates":[],"affectedComponents":[{"id":"49lgd3zs7wbg","name":"Cloud backups","status":"degraded_performance","created_at":"2017-07-06T20:50:26.571Z","updated_at":"2026-04-23T09:15:44.525Z","position":3,"description":"Some customers may be experiencing issues with cloud backups failing due to the error: \"File upload failed.\" We have implemented changes and are currently monitoring the situation. Our team is actively working to ensure the issue is fully resolved.","showcase":false,"start_date":null,"group_id":"p5z9pc1fpmtf","page_id":"k481728pjqn6","group":false,"only_show_if_degraded":false}],"guid":"gnnqg2ww6gkx","originalData":{"id":"gnnqg2ww6gkx","name":"Barracuda Appliance Control : Configuration Backup to Cloud – Service Disruption","status":"monitoring","created_at":"2026-04-23T09:15:44.500Z","updated_at":"2026-04-23T09:31:19.740Z","monitoring_at":"2026-04-23T09:31:19.710Z","resolved_at":null,"impact":"minor","shortlink":"https://stspg.io/4brdpjr7ktn5","started_at":"2026-04-23T09:15:44.494Z","page_id":"k481728pjqn6","incident_updates":"[Circular Reference]","components":"[Circular Reference]","reminder_intervals":null},"source":"api","vendor":"Barracuda Networks","vendorId":"barracuda","_parsedIsResolved":false,"_parsedStartTime":"2026-04-23T09:15:44.494Z","_parsedEndTime":null},{"id":"tag:status.redhat.com,2005:Incident/28729618","title":"AWS Outage: me-central","description":"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