TeraSwitch incident

AWS Tokyo - Ongoing AWS traffic detours

Resolved after 5 hours 12 minutes, affecting Global External Internet and TYO1 - Tokyo, Japan and 1 more, on September 3, 2026.

identified Sep 03, 2026, 02:52 PM UTC

Teraswitch has been tracking AWS Tokyo traffic taking long paths into TYO1/2/3. Local peering is disabled on the AWS side, and AWS transit traffic is selecting Singapore as a preferred hop over Tokyo. We are working on temporary solutions while AWS resolves the issue(s).

Started
Sep 03, 2026, 02:52 PM UTC
Resolved
Sep 03, 2026, 08:04 PM UTC
Duration
5h 12m
Detected by Pingoru
Sep 03, 2026, 02:52 PM UTC

Affected components

Global External InternetTYO1 - Tokyo, JapanTYO2 - Tokyo, JapanTYO3 - Tokyo, Japan

Update timeline

  1. identified Sep 03, 2026, 02:52 PM UTC

    Teraswitch has been tracking AWS Tokyo traffic taking long paths into TYO1/2/3. Local peering is disabled on the AWS side, and AWS transit traffic is selecting Singapore as a preferred hop over Tokyo. We are working on temporary solutions while AWS resolves the issue(s).

  2. resolved Sep 03, 2026, 08:04 PM UTC

    AWS has restored normal operation in the TYO market.

Your product runs on more than TeraSwitch

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →