GoTab incident

Heroku DNS Resolution Outage

Major Resolved View vendor source →

GoTab experienced a major incident on August 24, 2022 affecting Uptime and Heroku, lasting 3h 8m. The incident has been resolved; the full update timeline is below.

Started
Aug 24, 2022, 12:37 AM UTC
Resolved
Aug 24, 2022, 03:45 AM UTC
Duration
3h 8m
Detected by Pingoru
Aug 24, 2022, 12:37 AM UTC

Affected components

UptimeHeroku

Update timeline

  1. identified Aug 24, 2022, 12:37 AM UTC

    Our PaaS provider is experiencing an upstream DNS resolution problem that is causing all traffic to gotab.io to fail to resolve. Details are posted at https://status.heroku.com/incidents/2453

  2. identified Aug 24, 2022, 01:36 AM UTC

    A temporary workaround has been put in place to route traffic to our origin servers, bypassing Heroku's DNS servers.

  3. identified Aug 24, 2022, 02:02 AM UTC

    Heroku enginees have worked with their upstream DNS providers and a fix is being deployed at this time.

  4. monitoring Aug 24, 2022, 03:04 AM UTC

    Heroku incident #2453 reports that a fix has been deployed by their upstream DNS vendor and connectivity has been restored. We will continue to monitor and update accordingly.

  5. resolved Aug 24, 2022, 03:45 AM UTC

    This incident has been resolved.