Trestle Outage History

Trestle is up right now

Pingoru has recorded 4 incidents for Trestle: 1 in the last 12 months and 0 in the last 90 days.

Source: status.trestleiq.com

4incidents recorded
1last 12 months
0last 90 days
56 minutestypical duration
Incidents per month
012JulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%JulAugSepOct0%
Pingoru began tracking Trestle in July 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
July 202611 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 518 (0%)

Incidents, newest first

Notice July 24, 2026 Connecivity issues impacting multiple AWS services in the US-WEST-2 Region from AWS 55m Phone Validation API, Real Contact API, Address Validation API, Reverse Phone API and 4 more

Started Jul 24, 2026, 12:13 PM UTC· resolved Jul 24, 2026, 01:09 PM UTC

  1. identified Jul 24, 2026, 12:13 PM UTC

    https://health.aws.amazon.com/health/status Connectivity Issues Jul 24 4:56 AM PDT AWS are seeing initial signs of recovery and continues to work toward full recovery. Jul 24 4:40 AM PDT AWS are investigating connectivity issues impacting multiple AWS services in the US-WEST-2 Region.

  2. resolved Jul 24, 2026, 01:09 PM UTC

    [RESOLVED] Connectivity Issues

Read the full incident report →

Notice March 15, 2025 Temporary DNS resolution failure –

Started Mar 15, 2025, 12:00 PM UTC· resolved Mar 15, 2025, 12:00 PM UTC

  1. resolved Mar 18, 2025, 03:57 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 13, 2025 Internal Key Migration – Phone Validation API, Real Contact API, Reverse Phone API, Caller Identification API and 1 more

Started Feb 13, 2025, 01:45 PM UTC· resolved Feb 13, 2025, 01:45 PM UTC

  1. resolved Feb 13, 2025, 01:45 PM UTC

    Internal Key migration resulted in errors. No customer impact.

Read the full incident report →