Gadget - Notice history

All systems operational

Code editing - Operational

100% - uptime
Dec 2024 · 99.859%Jan 2025 · 99.944%Feb · 100.00%

Previous page

Next page

Dec 2024
Jan 2025
Feb 2025

API writes - Operational

100% - uptime
Dec 2024 · 99.853%Jan 2025 · 99.989%Feb · 100.00%

Previous page

Next page

Dec 2024
Jan 2025
Feb 2025

API reads - Operational

100% - uptime
Dec 2024 · 99.855%Jan 2025 · 99.994%Feb · 100.00%

Previous page

Next page

Dec 2024
Jan 2025
Feb 2025

Notice history

Feb 2025

No notices reported this month

Jan 2025

Timeout booting application servers
  • Resolved
    Resolved

    Automation: This incident has been resolved.

  • Investigating
    Investigating

    We are currently investigating this incident.

Timeout booting application servers
  • Resolved
    Resolved

    Automation: This incident has been resolved.

  • Investigating
    Investigating

    We are currently investigating this incident.

GGT_INTERNAL_ERROR: Can't add new pre-shutdown operations to a TreeOwner that is already shutting down
  • Resolved
    Resolved
    This incident has been resolved.
  • Identified
    Identified

    We shipped some changes that caused this error to occur, making app's editors unable to load and environments unable to make changes. We rolled back the changes and the error has been resolved.

Automated incident detected, the team is investigating and will add more details here
  • Resolved
    Resolved

    Automation: This incident has been resolved.

  • Investigating
    Investigating

    We are currently investigating this incident.

Performance degredation for session model reads and writes
  • Resolved
    Resolved
    This incident has been resolved.
  • Identified
    Identified

    The datastore powering Gadget's session model is experiencing elevated latencies. We're investigating.

Dec 2024

Minor unavailability - database failover
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring

    The standby instance has taken over and traffic is flowing as expected. We're monitoring to ensure no further action is necessary.

  • Investigating
    Investigating

    Our main database instance has failed and the automated failover is switching to the standby instance.

Search Requests Timing Out
  • Resolved
    Resolved
    This incident has been resolved.
  • Identified
    Identified
    We are continuing to work on a fix for this incident.
API reads & writes unavailable
  • Resolved
    Resolved

    The configuration change which likely lead to this incident has been reverted and all components are stable.

  • Monitoring
    Monitoring

    This incident has been resolved, but we're monitoring to make sure there's no further issues

  • Investigating
    Investigating

    We are currently investigating this incident.

Automated incident detected, the team is investigating and will add more details here
  • Resolved
    Resolved

    Automation: This incident has been resolved.

  • Investigating
    Investigating

    We are currently investigating this incident.

Automated incident detected, the team is investigating and will add more details here
  • Resolved
    Resolved

    Automation: This incident has been resolved.

  • Investigating
    Investigating

    We are currently investigating this incident.

Dec 2024 to Feb 2025

Next