All 11 services are operating normally.
Affects: Noida - Availability Region ap-south-3b
Window: 25 Sept 2026, 23:30-00:00 IST (30 minutes). A planned router reboot was performed during the maintenance window. Network services in the availability region saw a brief interruption. Routing, BGP sessions and connectivity were verified on completion; all services normal.
Affected: 12 Aug 2026 (Outage — a published incident affected this service.); 23 Sep 2026 (Degraded — a published incident affected this service.); 26 Sep 2026 (Degraded — a published incident affected this service.)
Affected: 12 Aug 2026 (Outage — a published incident affected this service.); 23 Sep 2026 (Degraded — a published incident affected this service.); 26 Sep 2026 (Degraded — a published incident affected this service.)
Affected: 12 Aug 2026 (Outage — a published incident affected this service.); 14 Aug 2026 (Degraded — a published incident affected this service.); 23 Sep 2026 (Degraded — a published incident affected this service.); 26 Sep 2026 (Degraded — a published incident affected this service.); 27 Sep 2026 (Maintenance — a published incident affected this service.)
Affected: 12 Aug 2026 (Outage — a published incident affected this service.); 14 Aug 2026 (Degraded — a published incident affected this service.); 23 Sep 2026 (Degraded — a published incident affected this service.); 26 Sep 2026 (Degraded — a published incident affected this service.)
Affected: 12 Aug 2026 (Outage — a published incident affected this service.); 14 Aug 2026 (Degraded — a published incident affected this service.); 23 Sep 2026 (Degraded — a published incident affected this service.); 26 Sep 2026 (Degraded — a published incident affected this service.)
Managed Apps
Affected: 12 Aug 2026 (Outage — a published incident affected this service.); 23 Sep 2026 (Degraded — a published incident affected this service.); 26 Sep 2026 (Degraded — a published incident affected this service.)
Affects: Managed Apps Platform, Noida - Availability Region ap-south-3a, Api Gateway ap-south-3, Noida - Availability Region ap-south-3b, Serverless fn ap-south-3, Ai Automation
Window: 26 Sept 2026, 22:15-22:29 IST (15 minutes). Emergency maintenance was carried out on a core router serving our Noida facility. Network services saw brief connectivity interruptions during the activity, which completed in under 15 minutes. Routing, BGP sessions and connectivity were verified afterwards and all services confirmed normal.
Affects: Managed Apps Platform, Noida - Availability Region ap-south-3a, Api Gateway ap-south-3, Noida - Availability Region ap-south-3b, Serverless fn ap-south-3, Ai Automation
Window: 23 Sept 2026, 22:00-22:29 IST (30 minutes). The primary upstream transit link for our Noida facility failed. Traffic shifted automatically to the backup carrier and services stayed available throughout; some customers may have seen briefly elevated latency while routing settled. The carrier restored the primary link after 30 minutes and traffic shifted back. No loss of availability at any point — the failover behaved as designed. Reported here because latency was measurably affected.
Affects: Api Gateway ap-south-3, Noida - Availability Region ap-south-3b, Serverless fn ap-south-3
Window: 14 Aug 2026, 20:00-20:15 IST (16 minutes). Packet loss was reported on a core router serving our Noida racks. An emergency firmware update and reboot were carried out in a 15-minute window. Traffic was rerouted during the reboot and some connections were briefly interrupted. Root cause: a defect in the router's firmware causing memory leaks and hardware-offload faults. The update resolved it and traffic volumes returned to normal immediately afterwards.
Affects: Managed Apps Platform, Noida - Availability Region ap-south-3a, Api Gateway ap-south-3, Noida - Availability Region ap-south-3b, Serverless fn ap-south-3, Ai Automation
Window: 12 Aug 2026, 13:52-17:37 IST (3h 45m). A volumetric DDoS attack directed at another tenant of our upstream provider's network degraded connectivity for Noida-hosted services. Impact came in two windows — 13:52-14:25 and 17:10-17:37 IST — totalling about one hour inside the period above. Compute and functions continued running; what degraded was reachability. Root cause: the attack peaked at roughly 60 Gbps / 6 Mpps and was TCP-based, completing a valid three-way handshake. It therefore passed the provider's stateful inline inspection and never triggered automatic scrubbing. Rate limiting was added to the scrubbing rules at 17:36 IST and traffic returned to normal. The provider is changing their rules so this pattern is caught automatically. Customers whose workloads were affected may be eligible for SLA credits — please contact support.
Affects: Noida - Availability Region ap-south-3a, Api Gateway ap-south-3, Serverless fn ap-south-3
Window: 6 Apr 2026, 15:52-15:55 IST (3 minutes). Planned network infrastructure maintenance in Noida ap-south-3a, part of ongoing capacity work by our facility provider. The window lasted three minutes, during which some customers may have seen brief added latency. Routing and connectivity were verified normal on completion.
Affects: Noida - Availability Region ap-south-3a, Api Gateway ap-south-3, Noida - Availability Region ap-south-3b, Serverless fn ap-south-3
Window: 2 Apr 2026, 22:55-23:13 IST (19 minutes). Our upstream provider absorbed a volumetric DDoS attack that their automated systems did not flag. Both Noida availability regions saw degraded network connectivity for roughly 18 minutes while mitigation was applied by hand. Instances and functions kept running throughout — the impact was reachability into the Noida region. Control planes are AWS-hosted and were unaffected, so the console and APIs stayed available. Follow-up: the provider's automated detection did not classify the traffic pattern as an attack. Manual mitigation restored normal traffic at 23:13 IST.
Uptime is derived from incidents published to our status provider since each service was added (earliest 2026-07-02), and refined by our own checks as they accumulate. Inferred days are shown muted, and days with no basis are grey rather than assumed green.
Subscriptions are not switched on yet. They will be shortly — in the meantime the feeds below carry every incident.
Answers from our docs, instantly
Checking…
