Created Task Error
Timeline · 1 update
- resolved Feb 24, 2025, 02:32 PM UTC
Due to an internal service failure, an anomaly has occurred, rendering the service unavailable.
Tripo Outage History
Tripo is up right nowTripo had 3 outages in the last 2 years totaling 7h 0m of downtime, averaging 0.1 incidents per month.
There were 3 Tripo outages since November 19, 2024 totaling 7h 0m of downtime. Each is summarised below. Incident details, duration, and resolution information.
Openapi Server Timeout
Affected: Openapi
Timeline · 2 updates
- identified Dec 11, 2024, 03:00 AM UTC
Internal error leading to high failure rate
- resolved Dec 11, 2024, 05:53 AM UTC
This incident has been resolved.
This is an example incident
Timeline · 4 updates
- investigating Nov 20, 2024, 11:54 AM UTC
When your product or service isn’t functioning as expected, let your customers know by creating an incident. Communicate early, even if you don’t know exactly what’s going on.
- identified Nov 20, 2024, 11:54 AM UTC
As you continue to work through the incident, update your customers frequently.
- monitoring Nov 20, 2024, 11:54 AM UTC
Let your users know once a fix is in place, and keep communication clear and precise.
- resolved Nov 20, 2024, 11:54 AM UTC
Empathize with those affected and let them know everything is operating as normal.