Pushy Outage History
Pushy is up right nowPingoru has recorded 516 incidents for Pushy: 7 in the last 12 months and 3 in the last 90 days.
Incidents, newest first
Minor October 7, 2026 Pushy API uptime incident post-mortem – API
Started Oct 07, 2026, 02:36 PM UTC· resolved Oct 07, 2026, 02:36 PM UTC
- investigating Oct 07, 2026, 02:36 PM UTC
First, we'd like to sincerely apologize for any inconvenience caused by this incident, and appreciate your patience while we worked to resolve the issue. The Pushy API experienced an uptime incident today that resulted in authentication failures and elevated 4xx API responses for approximately 45 minutes. During this period, some API requests were unable to authenticate successfully, which impacted the ability to send notifications. The underlying cause was a bug introduced as part of a software rollout. After identifying the issue, our engineering team promptly rolled back the affected deployment, which restored normal authentication and API functionality. The issue has now been fully resolved, and normal service has been restored. To reduce the likelihood of similar incidents in the future, we are reviewing our deployment and testing procedures and implementing additional safeguards around rollouts. If you have any questions or continue to experience problems, please contact our support team. Once again, we sincerely apologize for the inconvenience caused by this incident and appreciate your patience and understanding.
Minor October 7, 2026 API: Incident Resolved – API
Started Oct 07, 2026, 01:00 PM UTC· resolved Oct 07, 2026, 01:00 PM UTC
- investigating Oct 07, 2026, 01:00 PM UTC
The Pushy API is now back in full operational capacity.
Minor April 19, 2026 Pushy API uptime incident post-mortem – API
Started Apr 19, 2026, 06:24 AM UTC· resolved Apr 19, 2026, 06:24 AM UTC
- investigating Apr 19, 2026, 06:24 AM UTC
First, we'd like to sincerely apologize for any inconvenience caused by this incident, and appreciate your patience while we worked to resolve the issue. The Pushy API experienced an uptime incident today that caused elevated API response times, intermittent 5xx errors, and slower notification delivery for approximately 30 minutes. The underlying cause was a sudden burst of traffic that resulted in high latency on the Pushy primary MongoDB database. This database latency intermittently impacted API performance and notification delivery speeds as a result. Our engineering team investigated the issue and implemented corrective measures. The underlying problem has now been fully resolved, and normal service has been restored. To reduce the likelihood of similar incidents in the future, we have implemented additional safeguards and monitoring improvements to better handle sudden traffic spikes. If you have any questions or continue to experience problems, please contact our support team. Once again, we apologize for any inconvenience caused by this issue.
Minor April 19, 2026 API health check passed – API
Started Apr 19, 2026, 05:18 AM UTC· resolved Apr 19, 2026, 05:18 AM UTC
- investigating Apr 19, 2026, 05:18 AM UTC
The service is now operational.
Minor January 30, 2026 API: Elevated Error Rates (5xx) – API
Started Jan 30, 2026, 04:11 PM UTC· resolved Jan 30, 2026, 04:11 PM UTC
- investigating Jan 30, 2026, 04:11 PM UTC
We've resolved an issue that lasted 3 minutes, where elevated 5xx API error rates affected a small percentage of requests after migration to a new Redis cluster. API error rates are back to normal. We apologize for any inconvenience caused by this issue.