Search results
20 results for “api shutdown” · semantic + keyword ranking
- IncidentAPI Down
We deployed a change that caused the Rippling app to be unresponsive. We've
following today's service interruption in RCS message opt-out requests via the Channel Manager API, which began at 2026-07-30 06:30:00 UTC. Full resolution has been confirmed effective
- IncidentSmartsheet Application & API
action to reduce the load on the system at 7:48 AM Pacific Time. The shutdown of these backend systems caused delays for Webhooks, Connectors (Jira and Salesforce integration), Resource Views
- IncidentSmartsheet Application & API
reduce the load on the system at 11:33 AM Pacific Standard Time. The shutdown of these backend systems caused delays for Webhooks, Connectors (Jira and Salesforce integration), Resource Views, and updates
- IncidentApplication Outage
This incident has been resolved.
- IncidentSmartsheet Application & API
took action to reduce the load on the system at 8:20 AM PST. The shutdown of these backend systems caused delays for Webhooks, Connectors (Jira and Salesforce integration), and Resource Views
- IncidentApplication Outage
Everything is back to normal. We apologize for the inconvenience. A postmortem will be published soon.
API servers were inaccessible. Resolved
- IncidentUpdated Recording Script Bug
recording script to production. This version had a bug which could cause some Javascript APIs and events to throw. These errors resulted in an impact to our customer's end users. This … unexpected recording script state, triggered by a race condition. The cleanup code in shutdown() didn’t deal properly with this case, and would (a) throw exceptions from input change events
API services were briefly unavailable for a few minutes during a database restart. All services are now back online and working normally
This incident has been resolved.
- Incident[Developer API] API Outage
This incident has been resolved.
- IncidentApplication Outage
This incident has been resolved.
- IncidentAPI Service Degradation
API services have been fully restored and are operating normally
- Incident[Developer API] API Outage
This incident has been resolved.
- Incident[Developer API] API Outage
This incident has been resolved.
- IncidentAPI Server Outage
API servers have been healthy since the unhealthy ones were replaced with new ones
- Incident[Developer API] API Outage
This incident has been resolved.
- IncidentCalling currently unavailable
This incident has been resolved.
- IncidentCalling outage
This incident has been resolved.