Pushy https://status.pushy.me/ 2026-04-10T08:36:38+00:00 Pushy API: Elevated Error Rates (5xx) https://status.pushy.me/incident/850/ 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.

]]> 2026-01-30T16:11:13+00:00 Pushy API high latency resolved https://status.pushy.me/incident/849/ The Pushy API is now back in full operational capacity. The duration of the incident was 10 minutes. We apologize for any inconvenience caused. Thanks for your patience and understanding as we work to investigate the underlying cause.

]]> 2024-10-19T14:18:06+00:00 Pushy API high latency https://status.pushy.me/incident/848/ We're investigating an issue that is causing high latency in the API.

]]> 2024-10-19T13:39:45+00:00 Pushy API: Elevated Error Rates (4xx) https://status.pushy.me/incident/847/ We've resolved an issue where elevated 404 API error rates started to appear for a small percentage of requests after migration to a new API Load Balancer.

To remediate the incident, we have immediately deployed an update to the Load Balancer configuration. API error rates are back to normal.

We apologize for any inconvenience caused by this issue.

]]> 2024-10-05T15:16:00+00:00 Pushy Notification Service connectivity issue for Android 9 and older https://status.pushy.me/incident/846/ We've identified and resolved a connectivity issue for some devices running Android 9 and older. This was caused by a yearly TLS certificate update, in which the new intermediary certificate was not trusted on these older Android devices. We've transitioned to a new TLS certificate provider which is trusted all the way down to Android 2.1. We greatly apologize for any inconvenience caused.

]]> 2024-09-27T13:36:00+00:00 Pushy API high latency resolved https://status.pushy.me/incident/844/ The Pushy API is now back in full operational capacity. The duration of the incident was 5 minutes. We apologize for any inconvenience caused. Thanks for your patience and understanding as we work to investigate the underlying cause.

]]> 2024-06-21T15:28:49+00:00 Pushy API health check failed https://status.pushy.me/incident/843/ We're investigating an issue that is causing the health check to fail for the API.

]]> 2024-06-21T15:07:57+00:00 Pushy API health check passed https://status.pushy.me/incident/842/ The service is now operational.

]]> 2024-04-05T01:34:11+00:00 Pushy API high latency https://status.pushy.me/incident/841/ The Pushy API is now back in full operational capacity. The duration of this incident was 7 minutes. We apologize for any inconvenience caused. Thanks for your patience and understanding as we work to investigate the underlying cause.

]]> 2024-04-05T01:31:47+00:00 Pushy API health check failed https://status.pushy.me/incident/840/ We're investigating an issue that is causing the health check to fail for the API.

]]> 2024-04-05T01:13:53+00:00 Pushy Website high latency https://status.pushy.me/incident/839/ We apologize for the multiple e-mails sent out regarding a false alarm for website high latency. The service is operating normally.

]]> 2023-06-27T13:38:17+00:00 Pushy API: Ongoing maintenance (no planned impact) https://status.pushy.me/incident/816/ We will be performing maintenance on Monday, June 26th, at 10AM EST time, to upgrade the major Node.js version of our API stack. There should be minimal performance degradation and no service disruption during this time.

]]> 2023-06-26T13:23:00+00:00 Pushy Redis: Maintenance scheduled for Saturday https://status.pushy.me/incident/815/ We will be performing maintenance on Saturday, January 12th, at 10AM EST time, to upgrade the major version of our redis cluster. There should be minimal performance degradation and no service disruption during this time.

]]> 2023-01-12T15:33:35+00:00 Pushy Database: Maintenance completed https://status.pushy.me/incident/814/ We've finished conducting maintenance to improve the latency and performance of the database cluster. There was minimal performance degradation during a period of 2 hours.

]]> 2022-09-13T12:23:04+00:00 Pushy Database: Maintenance in progress https://status.pushy.me/incident/813/ We're performing maintenance to improve the latency and performance of the database cluster. There should be minimal performance degradation and no service disruption during this time.

]]> 2022-09-13T09:55:00+00:00 Pushy False Alarm: Notification Service health check failure https://status.pushy.me/incident/812/ This is a false alarm. You may safely ignore the previous e-mail sent regarding Notification Service health check failure. The notification service is fully operational and did not incur any uptime issue.

]]> 2022-09-10T12:27:56+00:00 Pushy Notification Service health check failed https://status.pushy.me/incident/811/ We're investigating an issue that is causing the health check to fail for the Notification Service.

]]> 2022-09-10T12:18:00+00:00 Pushy Notification service connectivity issue: Resolution https://status.pushy.me/incident/810/ Thanks for your patience and understanding as we worked to investigate and resolve this issue ASAP.

Due to an unexpected influx of new traffic, several servers in the MQTT notification cluster became overwhelmed and started timing out, causing intermittent connection errors. The incident lasted approximately 2.5 hours. We have resolved the issue ASAP and are taking steps to prevent it from reoccurring in the future.

We sincerely apologize for any inconvenience caused by this incident.

]]> 2022-01-18T03:38:30+00:00 Pushy Notification service connectivity issue https://status.pushy.me/incident/809/ We're investigating an issue that is causing connectivity timeouts in the Notification Service.

]]> 2022-01-18T01:19:00+00:00 Pushy API high latency: Resolution https://status.pushy.me/incident/808/ The Pushy API is now back in full operational capacity. The database cluster became temporarily unavailable following a AWS firewall configuration change which had unintentionally limited access. The duration of this incident was 20 minutes. Thanks for your patience and understanding as we worked to investigate and resolve this issue ASAP.

]]> 2021-12-20T17:09:52+00:00 Pushy API high latency https://status.pushy.me/incident/806/ We're investigating an issue that is causing high latency in the API.

]]> 2021-12-20T16:46:18+00:00 Pushy Notification service connectivity issue: Resolution https://status.pushy.me/incident/804/ We've resolved an issue regarding temporary connectivity timeouts for a percentage of Android devices which lasted approximately 60 minutes. The notification service is now back in full operational capacity.

Thanks for your patience and understanding as we worked to investigate and resolve this issue ASAP.

]]> 2021-11-08T23:56:00+00:00 Pushy Notification service connectivity issue https://status.pushy.me/incident/805/ We're investigating an issue that is causing connection timeouts in the Notification Service.

]]> 2021-11-08T22:56:00+00:00 Pushy Notification service timeouts: Resolution https://status.pushy.me/incident/802/ A sudden surge in connected devices has resulted in temporary connection timeouts over the past few hours for some Android and Electron devices. The notification service has been scaled accordingly, and is now back in full operational capacity.

Thanks for your patience and understanding as we worked to investigate and resolve this issue ASAP.

]]> 2021-09-30T19:03:00+00:00 Pushy Notification service timeouts https://status.pushy.me/incident/803/ We're investigating an issue that is causing connection timeouts in the Notification Service.

]]> 2021-09-30T16:03:00+00:00 Pushy API high latency: Resolution https://status.pushy.me/incident/801/ The Pushy API is now back in full operational capacity.

The primary database server has fully completed its resynchronization following an AWS EC2 / EBS outage in the us-east-1b region. The impact of this outage was 10 minutes of Pushy API downtime, followed by 14 hours of performance degradation while the primary was resynchronizing. During this time, 99% of API requests were served in 10-50ms, and the remaining 1% timed out.

Thanks for your patience and understanding as we worked to investigate and resolve this issue ASAP.

]]> 2021-09-27T18:24:49+00:00 Pushy API high latency: Update https://status.pushy.me/incident/800/ The Pushy database cluster is still recovering after an AWS EC2 / EBS volume outage in the 'us-east-1b' region, where the primary Pushy database is hosted. For a period of 4-5 hours, our primary database was completely unreachable due to an I/O cutoff from its EBS volumes, and so we had failed back to a secondary database quickly, within 10 minutes of the incident manifesting.

5 hours later, when AWS has restored connectivity to EBS volumes within the us-east-1b region, the primary database has gone out of sync, and is currently undergoing a full resync. This is causing slightly degraded performance due to increased resource contention to serve both API requests and to resync the primary database server.

The Pushy API is currently operational, although there are temporary periods of degraded performance while latency spikes. The resync is expected to complete within the next 2 hours, after which API latency should return to expected levels of ~15ms average.

We deeply apologize for the impact and inconvenience this has had on your reliable notification delivery experience. Thanks for your patience and understanding as we work to continue resolving this issue ASAP. We will post an update when it is fully resolved.

]]> 2021-09-27T14:25:45+00:00 Pushy API high latency: Update https://status.pushy.me/incident/769/ An underlying AWS networking issue with our primary database server has caused a complete API outage for a total duration of 10 minutes. Since the networking outage was only partial, it prevented secondary database members from stepping in to become the primary and continuing to serving requests as they have been able to connect, while the rest of the servers have not.

After 10 minutes of API downtime, the Pushy API is now back in working order. We apologize for any inconvenience this has had on your reliable notification delivery experience. Thanks for your patience and understanding as we worked to investigate and resolve this issue ASAP.

]]> 2021-09-27T03:55:00+00:00 Pushy API high latency https://status.pushy.me/incident/759/ We're investigating an issue that is causing high latency in the API.

]]> 2021-09-27T03:34:30+00:00 Pushy API health has stabilized https://status.pushy.me/incident/758/ API high latency spikes were incurred intermittently during the past 12 hours due to unanticipated load on the database cluster. We've optimized and scaled database cluster parameters to resolve this issue and prevent recurrence in the future.

The API has returned to full operational capacity.

We apologize for any impact on your reliable notification delivery experience as a result of this incident. Thanks for your patience and understanding as we worked to resolve this issue.

]]> 2021-09-24T22:18:00+00:00 Pushy API health has stabilized https://status.pushy.me/incident/756/ The API has returned to normal operational capacity.

]]> 2021-08-05T00:52:47+00:00 Pushy API high latency: Resolution https://status.pushy.me/incident/757/ We've identified and patched a memory leak in the Pushy API which has resulted in elevated latency and response times during the past 24 hours. Thanks for your patience and understanding as we worked to investigate and resolve this issue.

]]> 2021-08-04T22:43:00+00:00 Pushy API high latency https://status.pushy.me/incident/751/ We're investigating an issue that is causing high latency in the API.

]]> 2021-08-04T18:25:34+00:00 Pushy Support Center health has stabilized https://status.pushy.me/incident/744/ The Support Center has returned to normal operational capacity.

]]> 2021-07-31T01:34:00+00:00 Pushy Support Center health check failed https://status.pushy.me/incident/743/ We're investigating an issue that is causing the HTTP health check to fail for the Support Center.

]]> 2021-07-31T01:13:53+00:00 Pushy Notification service health has stabilized https://status.pushy.me/incident/742/ Thanks for your patience. The notification service has returned to full operational capacity.

Intermittent connection errors were incurred during a period of 30 minutes. We apologize for any impact on your reliable notification delivery experience as a result of this incident. All queued notifications are now being delivered as soon as any affected devices automatically reconnect to our service. Thanks for your patience and understanding as we worked to resolve this issue ASAP.

]]> 2021-04-19T23:14:00+00:00 Pushy Notification service health: Update https://status.pushy.me/incident/741/ Due to an unexpected influx of traffic, several servers in the MQTT notification service are overwhelmed and timing out, causing intermittent connection errors. We are actively working on resolution and the ETA for resolving this issue is 10 minutes.

]]> 2021-04-19T23:00:00+00:00 Pushy Notification service health check failed https://status.pushy.me/incident/740/ We're investigating an issue that is causing the HTTP health check to fail for the Notification Service.

]]> 2021-04-19T22:43:00+00:00 Pushy API health has stabilized https://status.pushy.me/incident/739/ The API has returned to full operational capacity. API high latency was incurred intermittently during a maximum period of 30 minutes. We've optimized and scaled database cluster parameters to resolve this issue and prevent recurrence in the future.

We apologize for any impact on your reliable notification delivery experience as a result of this incident. Thanks for your patience and understanding as we worked to resolve this issue.

]]> 2021-02-27T15:19:45+00:00 Pushy API high latency: Update https://status.pushy.me/incident/738/ We've identified a performance issue in the database cluster which is impacting the response time of requests sent to the API and are actively working on resolution.

]]> 2021-02-27T14:15:36+00:00 Pushy API high latency https://status.pushy.me/incident/737/ We're investigating an issue that is causing high latency in the API.

]]> 2021-02-27T14:04:37+00:00 Pushy API: Elevated Error Rates (Notification Collapse Key Incident) https://status.pushy.me/incident/736/ Elevated 4xx API error rates were caused by the introduction of a new feature to our service called "Notification Collapse Keys" which allows notification grouping, along with a limit of 32 characters for these keys. Up until yesterday, this feature did not exist and the parameter was being ignored. Requests with this parameter (collapse_key) containing a value larger than 32 characters have resulted in HTTP error 400.

To remediate the incident, we have immediately deployed an update which increased the limit of notification collapse keys from 32 to 100 characters. API error rates are back to normal.

An update: we have also identified an issue with APNs rejecting notifications with long collapse keys, and thus impacting iOS notification delivery resulting in error "InvalidCollapseId". We have rolled out a fix immediately, and iOS notification delivery is working as expected now.

]]> 2021-02-18T08:35:00+00:00 Pushy API health has stabilized https://status.pushy.me/incident/733/ We've optimized the database working set size to resolve this issue.

The API has returned to normal operational capacity.

]]> 2020-11-10T10:56:00+00:00 Pushy API high latency https://status.pushy.me/incident/732/ We're investigating an issue that is causing high latency in the API.

]]> 2020-11-10T10:36:23+00:00 Pushy Database: performance maintenance completed https://status.pushy.me/incident/729/ Maintenance has completed with no service degradation incidents.

]]> 2020-08-22T20:30:24+00:00 Pushy Database: performance improvement maintenance in progress https://status.pushy.me/incident/728/ We're performing maintenance to improve the latency and performance of the database cluster. There should be no performance degradation or service disruption during this time.

]]> 2020-08-22T14:32:58+00:00 Pushy Website health has stabilized https://status.pushy.me/incident/727/ The Website has returned to normal operational capacity.

]]> 2020-08-18T11:19:56+00:00 Pushy Website health check passed https://status.pushy.me/incident/725/ The HTTP endpoint is now operating as expected.

]]> 2020-08-18T11:18:52+00:00 Pushy Support Center health check failed https://status.pushy.me/incident/724/ We're investigating an issue that is causing the HTTP health check to fail for the Support Center.

]]> 2020-08-18T10:58:47+00:00 Pushy Support Center health has stabilized https://status.pushy.me/incident/723/ The Support Center has returned to normal operational capacity.

]]> 2020-07-17T21:40:00+00:00 Pushy Support Center health check failed https://status.pushy.me/incident/721/ We're investigating an issue that is causing the HTTP health check to fail for the Support Center.

]]> 2020-07-17T21:19:46+00:00 Pushy Support Center issue resolved https://status.pushy.me/incident/720/ Due to an issue with Zendesk Support, availability of the Support Center (support.pushy.me) was impacted for a total of 10 minutes. The issue is now resolved.

]]> 2020-05-28T20:04:07+00:00 Pushy Support Center health check failed https://status.pushy.me/incident/719/ We're investigating an issue that is causing the HTTP health check to fail for the Support Center.

]]> 2020-05-28T19:53:44+00:00 Pushy Notification Service: Deprecated TLS 1.1 & 1.0 support restored https://status.pushy.me/incident/718/ An update to the Notification Service temporarily dropped support for TLS 1.1 and 1.0. Deprecated TLS version support has been restored and the service is working optimally.

]]> 2020-05-17T22:28:00+00:00 Pushy Status Page has undergone a planned software update https://status.pushy.me/incident/715/ While we deployed an update to the Status Page to include a historical uptime timeline, it has become inaccessible for a short period of time. We've now rectified the underlying issue and the Status Page is in full operation.

Thanks for your patience and apologies for the e-mail spam.

]]> 2020-04-19T02:52:00+00:00 Pushy Status Page health check failed https://status.pushy.me/incident/714/ We're investigating an issue that is causing the HTTP health check to fail for the Status Page.

]]> 2020-04-19T02:32:59+00:00 Pushy Post-mortem: API & Notification service high latency & downtime (April 11, 2020) https://status.pushy.me/incident/713/ First off, we'd like to sincerely apologize for any impact this incident has had on your app's notification experience. Our core mission at Pushy has always been providing a fast, reliable, always-on notification service you can rely on 100% of the time. We have unfortunately failed to meet that expectation today.

The Pushy Pro API & notification service have experienced high latency and partial downtime over the past 8 hours due to a large-scale, sophisticated Denial of Service attack on our API. After further investigation and multiple attempts, we have been successful in blocking the attack and ensuring it will be blocked in the future to prevent any similar incidents.

The incident is now resolved and service is restored. Once again, we truly apologize for any inconvenience and negative impact caused by this incident.

We thank you for choosing Pushy. Please contact us if you have any questions or concerns.

]]> 2020-04-11T20:58:08+00:00 Pushy API health has stabilized https://status.pushy.me/incident/712/ The API has returned to normal operational capacity.

]]> 2020-04-11T20:06:13+00:00 Pushy API: Incident reclassified as DDoS attack - fix in progress https://status.pushy.me/incident/711/ We've identified a DDoS attack on the API which is causing this incident. We're working on restoring availability ASAP and blocking this attack vector. Thank you for your patience.

]]> 2020-04-11T18:16:54+00:00 Pushy Notification Service high latency https://status.pushy.me/incident/710/ We're investigating an issue that is causing high latency in the Notification Service.

]]> 2020-04-11T17:37:42+00:00 Pushy API: Issue identified & fix in progress https://status.pushy.me/incident/709/ We've identified the issue causing the incident and are working on a fix ASAP. Thank you for your patience.

]]> 2020-04-11T17:20:06+00:00 Pushy API high latency https://status.pushy.me/incident/708/ We're investigating an issue that is causing high latency in the API.

]]> 2020-04-11T13:07:04+00:00 Pushy Preventative DB maintenance https://status.pushy.me/incident/707/ We're performing preventative maintenance to reduce latency over the long-term. Small latency spikes may occur of avg. ~1000ms.

Update: Maintenance completed. Avg latency is now ~15ms.

]]> 2019-12-30T03:58:00+00:00 Pushy Database maintenance planned https://status.pushy.me/incident/706/ A planned database maintenance will occur in the next hour and will last approximately 1 hour. No downtime or high latency is expected.

]]> 2019-11-13T00:23:00+00:00 Pushy Status Page health check passed https://status.pushy.me/incident/705/ The HTTP endpoint is now operating as expected.

]]> 2019-10-27T07:09:29+00:00 Pushy Website health check failed https://status.pushy.me/incident/704/ We're investigating an issue that is causing the HTTP health check to fail for the Website.

]]> 2019-10-27T06:49:29+00:00 Pushy Website health check passed https://status.pushy.me/incident/703/ The HTTP endpoint is now operating as expected.

]]> 2019-10-26T08:14:03+00:00 Pushy Website health check failed https://status.pushy.me/incident/702/ We're investigating an issue that is causing the HTTP health check to fail for the Website.

]]> 2019-10-26T07:53:45+00:00 Pushy Primary DB server EBS volume rotated https://status.pushy.me/incident/701/ The AWS EBS volume was suffering from degraded performance due to an underlying AWS hardware issue. Volume replacement fixed all latency issues.

]]> 2019-10-02T22:09:18+00:00 Pushy API health has stabilized https://status.pushy.me/incident/698/ The API has returned to normal operational capacity.

]]> 2019-10-02T15:20:38+00:00 Pushy Primary DB server low on memory https://status.pushy.me/incident/696/ We are attempting a restart of the primary database server and scaling its memory to resolve the high latency incident.

]]> 2019-10-02T14:52:18+00:00 Pushy API high latency https://status.pushy.me/incident/695/ We're investigating an issue that is causing high latency in the API.

]]> 2019-10-02T14:33:31+00:00 Pushy API health has stabilized https://status.pushy.me/incident/694/ The API has returned to normal operational capacity.

]]> 2019-06-09T01:48:42+00:00 Pushy API high latency https://status.pushy.me/incident/693/ We're investigating an issue that is causing high latency in the API.

]]> 2019-06-09T01:18:50+00:00 Pushy API health has stabilized https://status.pushy.me/incident/692/ The API has returned to normal operational capacity.

]]> 2019-03-29T03:59:14+00:00 Pushy API high latency https://status.pushy.me/incident/691/ We're investigating an issue that is causing high latency in the API.

]]> 2019-03-29T03:37:30+00:00 Pushy API health has stabilized https://status.pushy.me/incident/690/ The API has returned to normal operational capacity.

]]> 2019-02-20T07:22:01+00:00 Pushy API high latency https://status.pushy.me/incident/689/ We're investigating an issue that is causing high latency in the API.

]]> 2019-02-20T07:01:52+00:00 Pushy API health has stabilized https://status.pushy.me/incident/688/ The API has returned to normal operational capacity.

]]> 2019-01-17T00:15:23+00:00 Pushy API high latency https://status.pushy.me/incident/687/ We're investigating an issue that is causing high latency in the API.

]]> 2019-01-16T23:55:23+00:00 Pushy API health has stabilized https://status.pushy.me/incident/686/ The API has returned to normal operational capacity.

]]> 2019-01-16T07:32:59+00:00 Pushy API high latency https://status.pushy.me/incident/685/ We're investigating an issue that is causing high latency in the API.

]]> 2019-01-16T07:04:39+00:00 Pushy API health has stabilized https://status.pushy.me/incident/684/ The API has returned to normal operational capacity.

]]> 2019-01-15T00:22:47+00:00 Pushy API high latency https://status.pushy.me/incident/683/ We're investigating an issue that is causing high latency in the API.

]]> 2019-01-14T23:59:10+00:00 Pushy API health has stabilized https://status.pushy.me/incident/682/ The API has returned to normal operational capacity.

]]> 2019-01-08T02:40:32+00:00 Pushy API high latency https://status.pushy.me/incident/681/ We're investigating an issue that is causing high latency in the API.

]]> 2019-01-08T02:20:30+00:00 Pushy API health has stabilized https://status.pushy.me/incident/680/ The API has returned to normal operational capacity.

]]> 2019-01-08T01:40:30+00:00 Pushy API high latency https://status.pushy.me/incident/679/ We're investigating an issue that is causing high latency in the API.

]]> 2019-01-08T01:15:19+00:00 Pushy API health has stabilized https://status.pushy.me/incident/678/ The API has returned to normal operational capacity.

]]> 2018-12-30T04:32:40+00:00 Pushy API high latency https://status.pushy.me/incident/677/ We're investigating an issue that is causing high latency in the API.

]]> 2018-12-30T04:12:10+00:00 Pushy API health has stabilized https://status.pushy.me/incident/676/ The API has returned to normal operational capacity.

]]> 2018-12-29T04:06:55+00:00 Pushy API high latency https://status.pushy.me/incident/675/ We're investigating an issue that is causing high latency in the API.

]]> 2018-12-29T03:46:26+00:00 Pushy API health has stabilized https://status.pushy.me/incident/674/ The API has returned to normal operational capacity.

]]> 2018-12-12T00:07:40+00:00 Pushy API high latency https://status.pushy.me/incident/673/ We're investigating an issue that is causing high latency in the API.

]]> 2018-12-11T23:47:12+00:00 Pushy API health has stabilized https://status.pushy.me/incident/672/ The API has returned to normal operational capacity.

]]> 2018-12-11T16:28:01+00:00 Pushy API high latency https://status.pushy.me/incident/671/ We're investigating an issue that is causing high latency in the API.

]]> 2018-12-11T16:07:32+00:00 Pushy API health has stabilized https://status.pushy.me/incident/670/ The API has returned to normal operational capacity.

]]> 2018-12-11T15:36:29+00:00 Pushy API high latency https://status.pushy.me/incident/669/ We're investigating an issue that is causing high latency in the API.

]]> 2018-12-11T15:06:13+00:00 Pushy API health has stabilized https://status.pushy.me/incident/668/ The API has returned to normal operational capacity.

]]> 2018-11-30T20:13:54+00:00 Pushy API high latency https://status.pushy.me/incident/667/ We're investigating an issue that is causing high latency in the API.

]]> 2018-11-30T19:51:44+00:00 Pushy Database maintenance completed https://status.pushy.me/incident/666/ We have finished optimizing the database to mitigate high latency issues.

]]> 2018-11-20T13:57:55+00:00 Pushy Database maintenance https://status.pushy.me/incident/665/ We will be conducting database maintenance over the next 5 hours. This purpose of this maintenance is performing optimizations that will prevent future incidents of high latency. No downtime is expected and service should operate normally, but short periods of high latency may occur during this period.

]]> 2018-11-20T11:30:00+00:00 Pushy API health has stabilized https://status.pushy.me/incident/662/ The API has returned to normal operational capacity.

]]> 2018-11-20T09:08:40+00:00 Pushy API high latency https://status.pushy.me/incident/661/ We're investigating an issue that is causing high latency in the API.

]]> 2018-11-20T08:48:31+00:00 Pushy API health has stabilized https://status.pushy.me/incident/660/ The API has returned to normal operational capacity.

]]> 2018-11-15T09:29:00+00:00 Pushy API high latency https://status.pushy.me/incident/659/ We're investigating an issue that is causing high latency in the API.

]]> 2018-11-15T09:00:19+00:00 Pushy API health has stabilized https://status.pushy.me/incident/658/ The API has returned to normal operational capacity.

]]> 2018-11-14T23:13:43+00:00 Pushy API high latency https://status.pushy.me/incident/657/ We're investigating an issue that is causing high latency in the API.

]]> 2018-11-14T22:53:38+00:00 Pushy API health has stabilized https://status.pushy.me/incident/656/ The API has returned to normal operational capacity.

]]> 2018-11-10T05:11:26+00:00 Pushy API high latency https://status.pushy.me/incident/655/ We're investigating an issue that is causing high latency in the API.

]]> 2018-11-10T04:51:21+00:00 Pushy API health has stabilized https://status.pushy.me/incident/654/ The API has returned to normal operational capacity.

]]> 2018-11-09T23:52:29+00:00 Pushy API high latency https://status.pushy.me/incident/653/ We're investigating an issue that is causing high latency in the API.

]]> 2018-11-09T23:32:24+00:00 Pushy API health has stabilized https://status.pushy.me/incident/652/ The API has returned to normal operational capacity.

]]> 2018-11-03T06:47:44+00:00 Pushy API high latency https://status.pushy.me/incident/651/ We're investigating an issue that is causing high latency in the API.

]]> 2018-11-03T06:27:37+00:00 Pushy API health has stabilized https://status.pushy.me/incident/650/ The API has returned to normal operational capacity.

]]> 2018-11-03T00:32:44+00:00 Pushy API high latency https://status.pushy.me/incident/649/ We're investigating an issue that is causing high latency in the API.

]]> 2018-11-03T00:12:36+00:00 Pushy API health has stabilized https://status.pushy.me/incident/648/ The API has returned to normal operational capacity.

]]> 2018-11-02T06:54:51+00:00 Pushy API high latency https://status.pushy.me/incident/647/ We're investigating an issue that is causing high latency in the API.

]]> 2018-11-02T06:34:24+00:00 Pushy API latency: Attempting various optimization strategies https://status.pushy.me/incident/646/ Two short periods of high latency (up from ~30ms to ~2 seconds per request, for two periods of up to 10 minutes) have affected the notification service due to sudden increased load.

We have stabilized the service and are attempting various latency optimization strategies. Further incidents will be posted if there are any further developments. We apologize for any inconvenience caused.

]]> 2018-11-01T16:55:00+00:00 Pushy API health has stabilized https://status.pushy.me/incident/645/ The API has returned to normal operational capacity.

]]> 2018-11-01T09:40:41+00:00 Pushy API high latency https://status.pushy.me/incident/644/ We're investigating an issue that is causing high latency in the API.

]]> 2018-11-01T09:20:35+00:00 Pushy API health has stabilized https://status.pushy.me/incident/643/ The API has returned to normal operational capacity.

]]> 2018-11-01T01:17:38+00:00 Pushy API high latency https://status.pushy.me/incident/642/ We're investigating an issue that is causing high latency in the API.

]]> 2018-11-01T00:57:33+00:00 Pushy Notification service update https://status.pushy.me/incident/641/ Due to an unexpected memory issue we have been obliged to issue a notification server update which requires all Android devices to reconnect to our service. Impact should be minimal with devices reconnecting in less than 5 minutes time automatically. No action is required on your end.

]]> 2018-09-25T12:46:00+00:00 Pushy Post-mortem: Notification service high latency https://status.pushy.me/incident/640/ High latency has affected the notification service for a period of 30 minutes due to memory pressure. We have stabilized the service. Further incidents will be posted if there are any further developments. We apologize for any inconvenience caused.

]]> 2018-08-30T21:30:00+00:00 Pushy Notification Service health has stabilized https://status.pushy.me/incident/639/ The Notification Service has returned to normal operational capacity.

]]> 2018-08-30T21:11:45+00:00 Pushy Notification Service high latency https://status.pushy.me/incident/638/ We're investigating an issue that is causing high latency in the Notification Service.

]]> 2018-08-30T20:47:24+00:00 Pushy Notification Service health has stabilized https://status.pushy.me/incident/636/ The Notification Service has returned to normal operational capacity.

]]> 2018-08-26T14:47:38+00:00 Pushy Notification Service high latency https://status.pushy.me/incident/637/ We're investigating an issue that is causing high latency in the Notification Service.

]]> 2018-08-26T14:01:00+00:00 Pushy API health has stabilized https://status.pushy.me/incident/635/ The API has returned to normal operational capacity.

]]> 2018-08-26T04:45:43+00:00 Pushy API: Elevated error rates https://status.pushy.me/incident/634/ We're investigating elevated 5xx error rates (5%) for requests to the API.

]]> 2018-08-26T04:25:00+00:00 Pushy Post-mortem: High API latency https://status.pushy.me/incident/633/ High latency has affected the service for a period of 4 minutes. We have managed to stabilize the service. Further incidents will be posted if there are any future developments. We apologize for any inconvenience caused.

]]> 2018-06-25T15:30:52+00:00 Pushy API health has stabilized https://status.pushy.me/incident/632/ The API has returned to normal operational capacity.

]]> 2018-06-25T15:22:47+00:00 Pushy API high latency https://status.pushy.me/incident/631/ We're investigating an issue that is causing high latency in the API.

]]> 2018-06-25T15:02:29+00:00 Pushy Post-mortem: High API latency https://status.pushy.me/incident/630/ High latency has affected the API for seven short bursts of 2 - 3 minutes each from 2:00AM UTC to 4:00AM UTC. No requests were dropped during this time. We have managed to stabilize the service. Further incidents will be posted if there are any future developments. We apologize for any inconvenience caused.

]]> 2018-06-08T04:34:45+00:00 Pushy API health has stabilized https://status.pushy.me/incident/629/ The API has returned to normal operational capacity.

]]> 2018-06-08T04:06:39+00:00 Pushy API high latency https://status.pushy.me/incident/624/ We're investigating an issue that is causing high latency in the API.

]]> 2018-06-08T02:04:15+00:00 Pushy Update: Notification service outage https://status.pushy.me/incident/623/ The MQTT notification service (Android) has experienced downtime in the past hours due to a large-scale Denial of Service attack on our service by an unknown party. We have been unsuccessful in blocking the attack. Instead, we have greatly over-provisioned compute resources to support the immense number of connections introduced by the attack.

Service has currently been restored. At this time we are continuing to monitor the attack as it is still ongoing. We are also investigating ways to detect and block Denial of Service attacks automatically to prevent similar incidents in the future.

Further incidents will be posted if there are any future developments. We truly apologize for any inconvenience caused by this Denial of Service attack.

]]> 2018-06-06T20:37:50+00:00 Pushy Notification Service health check passed https://status.pushy.me/incident/621/ The HTTP endpoint is now operating as expected.

]]> 2018-06-06T20:30:17+00:00 Pushy Notification Service health check failed https://status.pushy.me/incident/613/ We're investigating an issue that is causing the HTTP health check to fail for the Notification Service.

]]> 2018-06-06T13:37:50+00:00 Pushy Post-mortem: Notification service partial outage https://status.pushy.me/incident/612/ Notification service partial outage has affected the service for a period of less than 30 minutes due to unexpected load on the cluster. We have managed to stabilize the service. Further incidents will be posted if there are any future developments. We apologize for any inconvenience caused.

]]> 2018-06-05T23:28:00+00:00 Pushy Notification Service health check passed https://status.pushy.me/incident/611/ The HTTP endpoint is now operating as expected.

]]> 2018-06-05T15:36:09+00:00 Pushy Notification Service health check failed https://status.pushy.me/incident/610/ We're investigating an issue that is causing the HTTP health check to fail for the Notification Service.

]]> 2018-06-05T15:15:46+00:00 Pushy Post-mortem: High latency https://status.pushy.me/incident/609/ High latency has affected the service for a period of 15 minutes. We have managed to stabilize the service. Further incidents will be posted if there are any future developments. We apologize for any inconvenience caused.

]]> 2018-05-21T04:17:47+00:00 Pushy API health has stabilized https://status.pushy.me/incident/608/ The API has returned to normal operational capacity.

]]> 2018-05-21T04:14:26+00:00 Pushy API high latency https://status.pushy.me/incident/607/ We're investigating an issue that is causing high latency in the API.

]]> 2018-05-21T03:44:17+00:00 Pushy API health has stabilized https://status.pushy.me/incident/606/ The API has returned to normal operational capacity.

]]> 2018-05-01T04:13:38+00:00 Pushy API high latency https://status.pushy.me/incident/605/ We're investigating an issue that is causing high latency in the API.

]]> 2018-05-01T03:53:36+00:00 Pushy API health has stabilized https://status.pushy.me/incident/604/ The API has returned to normal operational capacity.

]]> 2018-04-22T12:18:16+00:00 Pushy API high latency https://status.pushy.me/incident/603/ We're investigating an issue that is causing high latency in the API.

]]> 2018-04-22T11:48:22+00:00 Pushy Post-mortem: High latency https://status.pushy.me/incident/602/ After additional periods of service degradation, we have managed to stabilize the service. Further incidents will be posted if there are any future developments.

]]> 2018-04-22T08:05:20+00:00 Pushy Notification Service health has stabilized https://status.pushy.me/incident/601/ The Notification Service has returned to normal operational capacity.

]]> 2018-04-22T07:52:06+00:00 Pushy Notification Service health check passed https://status.pushy.me/incident/600/ The HTTP endpoint is now operating as expected.

]]> 2018-04-22T07:51:46+00:00 Pushy Notification Service health check failed https://status.pushy.me/incident/599/ We're investigating an issue that is causing the HTTP health check to fail for the Notification Service.

]]> 2018-04-22T07:31:39+00:00 Pushy API health has stabilized https://status.pushy.me/incident/598/ The API has returned to normal operational capacity.

]]> 2018-04-22T07:10:13+00:00 Pushy API high latency https://status.pushy.me/incident/597/ We're investigating an issue that is causing high latency in the API.

]]> 2018-04-22T06:47:07+00:00 Pushy Post-mortem: High latency https://status.pushy.me/incident/596/ Over the past 30 minutes, we have been experiencing several short periods of high latency due to routine database maintenance. Maintenance has been completed and latency should be back to normal.

]]> 2018-04-22T06:16:55+00:00 Pushy API high latency https://status.pushy.me/incident/595/ We're investigating an issue that is causing high latency in the API.

]]> 2018-04-22T05:37:14+00:00 Pushy Post-mortem: High latency https://status.pushy.me/incident/594/ Over the past 24 hours, we have been experiencing several short periods of high latency due to excessive load on the database cluster. We would like to apologize for any negative effect this has had on the immediate delivery of notifications to your users.

After attempting several remediation strategies, we have been able to apply a solution that appears to be working quite well. We will be closely monitoring latency over the next few days to confirm that the issue is indeed resolved.

]]> 2018-03-23T01:24:00+00:00 Pushy API health has stabilized https://status.pushy.me/incident/593/ The API has returned to normal operational capacity.

]]> 2018-03-22T15:54:24+00:00 Pushy API high latency https://status.pushy.me/incident/592/ We're investigating an issue that is causing high latency in the API.

]]> 2018-03-22T15:34:08+00:00 Pushy API health has stabilized https://status.pushy.me/incident/591/ The API has returned to normal operational capacity.

]]> 2018-03-22T14:57:39+00:00 Pushy API high latency https://status.pushy.me/incident/590/ We're investigating an issue that is causing high latency in the API.

]]> 2018-03-22T14:37:35+00:00 Pushy API health has stabilized https://status.pushy.me/incident/589/ The API has returned to normal operational capacity.

]]> 2018-03-22T14:11:34+00:00 Pushy API high latency https://status.pushy.me/incident/588/ We're investigating an issue that is causing high latency in the API.

]]> 2018-03-22T13:47:32+00:00 Pushy API health has stabilized https://status.pushy.me/incident/587/ The API has returned to normal operational capacity.

]]> 2018-03-22T12:44:40+00:00 Pushy API high latency https://status.pushy.me/incident/586/ We're investigating an issue that is causing high latency in the API.

]]> 2018-03-22T12:24:12+00:00 Pushy API health has stabilized https://status.pushy.me/incident/585/ The API has returned to normal operational capacity.

]]> 2018-03-22T10:20:50+00:00 Pushy Website health has stabilized https://status.pushy.me/incident/584/ The Website has returned to normal operational capacity.

]]> 2018-03-22T10:19:15+00:00 Pushy Website high latency https://status.pushy.me/incident/583/ We're investigating an issue that is causing high latency in the Website.

]]> 2018-03-22T09:41:29+00:00 Pushy API high latency https://status.pushy.me/incident/582/ We're investigating an issue that is causing high latency in the API.

]]> 2018-03-22T08:58:29+00:00 Pushy API health has stabilized https://status.pushy.me/incident/581/ The API has returned to normal operational capacity.

]]> 2018-03-22T07:04:28+00:00 Pushy Website health has stabilized https://status.pushy.me/incident/580/ The Website has returned to normal operational capacity.

]]> 2018-03-22T07:03:56+00:00 Pushy Website high latency https://status.pushy.me/incident/579/ We're investigating an issue that is causing high latency in the Website.

]]> 2018-03-22T06:35:26+00:00 Pushy API high latency https://status.pushy.me/incident/578/ We're investigating an issue that is causing high latency in the API.

]]> 2018-03-22T06:32:08+00:00 Pushy API health has stabilized https://status.pushy.me/incident/577/ The API has returned to normal operational capacity.

]]> 2018-03-22T06:09:49+00:00 Pushy Website health has stabilized https://status.pushy.me/incident/576/ The Website has returned to normal operational capacity.

]]> 2018-03-22T05:58:17+00:00 Pushy Website high latency https://status.pushy.me/incident/575/ We're investigating an issue that is causing high latency in the Website.

]]> 2018-03-22T05:37:24+00:00 Pushy API high latency https://status.pushy.me/incident/574/ We're investigating an issue that is causing high latency in the API.

]]> 2018-03-22T05:34:06+00:00 Pushy API health has stabilized https://status.pushy.me/incident/573/ The API has returned to normal operational capacity.

]]> 2018-03-22T03:40:39+00:00 Pushy API high latency https://status.pushy.me/incident/572/ We're investigating an issue that is causing high latency in the API.

]]> 2018-03-22T02:19:09+00:00 Pushy Post-mortem: High latency https://status.pushy.me/incident/571/ Over the past few days, we have been experiencing several short periods of high latency during excessive bursts of traffic. We would like to apologize for any negative effect this has had on the immediate delivery of notifications to your users.

After attempting several remediation strategies, we have been able to find a solution that appears to be working quite well, by utilizing a Redis caching mechanism to drastically reduce load on the database cluster. We will be closely monitoring latency over the next few days to confirm that the issue is indeed resolved.

]]> 2018-03-11T23:36:49+00:00 Pushy Notification Service health has stabilized https://status.pushy.me/incident/570/ The Notification Service has returned to normal operational capacity.

]]> 2018-03-10T10:56:33+00:00 Pushy API health has stabilized https://status.pushy.me/incident/569/ The API has returned to normal operational capacity.

]]> 2018-03-10T10:53:21+00:00 Pushy Website health has stabilized https://status.pushy.me/incident/568/ The Website has returned to normal operational capacity.

]]> 2018-03-10T10:51:47+00:00 Pushy Notification Service high latency https://status.pushy.me/incident/567/ We're investigating an issue that is causing high latency in the Notification Service.

]]> 2018-03-10T10:36:20+00:00 Pushy Website high latency https://status.pushy.me/incident/566/ We're investigating an issue that is causing high latency in the Website.

]]> 2018-03-10T10:22:39+00:00 Pushy API high latency https://status.pushy.me/incident/565/ We're investigating an issue that is causing high latency in the API.

]]> 2018-03-10T10:01:37+00:00 Pushy Notification Service health has stabilized https://status.pushy.me/incident/564/ The Notification Service has returned to normal operational capacity.

]]> 2018-03-10T09:35:38+00:00 Pushy API health has stabilized https://status.pushy.me/incident/563/ The API has returned to normal operational capacity.

]]> 2018-03-10T09:27:36+00:00 Pushy Website health has stabilized https://status.pushy.me/incident/562/ The Website has returned to normal operational capacity.

]]> 2018-03-10T09:27:02+00:00 Pushy Notification Service high latency https://status.pushy.me/incident/561/ We're investigating an issue that is causing high latency in the Notification Service.

]]> 2018-03-10T09:10:25+00:00 Pushy Website high latency https://status.pushy.me/incident/560/ We're investigating an issue that is causing high latency in the Website.

]]> 2018-03-10T08:56:48+00:00 Pushy API high latency https://status.pushy.me/incident/559/ We're investigating an issue that is causing high latency in the API.

]]> 2018-03-10T08:50:27+00:00 Pushy API health has stabilized https://status.pushy.me/incident/558/ The API has returned to normal operational capacity.

]]> 2018-03-10T07:03:11+00:00 Pushy Website health has stabilized https://status.pushy.me/incident/557/ The Website has returned to normal operational capacity.

]]> 2018-03-10T06:46:22+00:00 Pushy Website high latency https://status.pushy.me/incident/556/ We're investigating an issue that is causing high latency in the Website.

]]> 2018-03-10T06:20:11+00:00 Pushy API high latency https://status.pushy.me/incident/555/ We're investigating an issue that is causing high latency in the API.

]]> 2018-03-10T06:14:14+00:00 Pushy API health has stabilized https://status.pushy.me/incident/554/ The API has returned to normal operational capacity.

]]> 2018-03-10T05:10:44+00:00 Pushy Website health has stabilized https://status.pushy.me/incident/553/ The Website has returned to normal operational capacity.

]]> 2018-03-10T05:08:01+00:00 Pushy Notification Service health has stabilized https://status.pushy.me/incident/552/ The Notification Service has returned to normal operational capacity.

]]> 2018-03-10T05:05:13+00:00 Pushy Notification Service high latency https://status.pushy.me/incident/551/ We're investigating an issue that is causing high latency in the Notification Service.

]]> 2018-03-10T04:35:55+00:00 Pushy Website high latency https://status.pushy.me/incident/550/ We're investigating an issue that is causing high latency in the Website.

]]> 2018-03-10T04:33:09+00:00 Pushy API high latency https://status.pushy.me/incident/549/ We're investigating an issue that is causing high latency in the API.

]]> 2018-03-10T04:27:15+00:00 Pushy High latency root cause under investigation https://status.pushy.me/incident/542/ Our service experienced high latency for short periods of up to 20 minutes in the past 24 hours. Investigation is still underway and we are attempting various solutions to prevent high latency from reoccurring. No API requests were dropped during these periods of high latency.

]]> 2018-03-09T15:44:00+00:00 Pushy API health has stabilized https://status.pushy.me/incident/548/ The API has returned to normal operational capacity.

]]> 2018-03-09T15:30:57+00:00 Pushy Website health has stabilized https://status.pushy.me/incident/547/ The Website has returned to normal operational capacity.

]]> 2018-03-09T15:29:15+00:00 Pushy Notification Service health has stabilized https://status.pushy.me/incident/546/ The Notification Service has returned to normal operational capacity.

]]> 2018-03-09T15:10:19+00:00 Pushy Notification Service high latency https://status.pushy.me/incident/545/ We're investigating an issue that is causing high latency in the Notification Service.

]]> 2018-03-09T14:48:11+00:00 Pushy Website high latency https://status.pushy.me/incident/544/ We're investigating an issue that is causing high latency in the Website.

]]> 2018-03-09T14:39:10+00:00 Pushy API high latency https://status.pushy.me/incident/543/ We're investigating an issue that is causing high latency in the API.

]]> 2018-03-09T14:36:19+00:00 Pushy API health has stabilized https://status.pushy.me/incident/541/ The API has returned to normal operational capacity.

]]> 2018-03-09T04:37:31+00:00 Pushy Notification Service health has stabilized https://status.pushy.me/incident/540/ The Notification Service has returned to normal operational capacity.

]]> 2018-03-09T04:30:03+00:00 Pushy Notification Service high latency https://status.pushy.me/incident/533/ We're investigating an issue that is causing high latency in the Notification Service.

]]> 2018-03-09T02:48:08+00:00 Pushy API high latency https://status.pushy.me/incident/532/ We're investigating an issue that is causing high latency in the API.

]]> 2018-03-09T02:47:25+00:00 Pushy Website health has stabilized https://status.pushy.me/incident/531/ The Website has returned to normal operational capacity.

]]> 2018-03-08T18:15:30+00:00 Pushy API health has stabilized https://status.pushy.me/incident/530/ The API has returned to normal operational capacity.

]]> 2018-03-08T18:14:15+00:00 Pushy Website high latency https://status.pushy.me/incident/529/ We're investigating an issue that is causing high latency in the Website.

]]> 2018-03-08T17:55:23+00:00 Pushy API high latency https://status.pushy.me/incident/528/ We're investigating an issue that is causing high latency in the API.

]]> 2018-03-08T17:27:22+00:00 Pushy Website health has stabilized https://status.pushy.me/incident/527/ The Website has returned to normal operational capacity.

]]> 2018-02-15T20:27:33+00:00 Pushy Website high latency https://status.pushy.me/incident/526/ We're investigating an issue that is causing high latency in the Website.

]]> 2018-02-15T20:02:22+00:00 Pushy 24-hour database maintenance https://status.pushy.me/incident/525/ We will be conducting database maintenance over the next 24 hours. This purpose of this maintenance is performing modifications that will prevent future incidents of high latency. No downtime is expected and service should operate normally, but short periods of high latency may occur during this period. If high latency does occur, it will be reported on this page.

]]> 2018-01-21T02:43:00+00:00 Pushy High latency root cause under investigation https://status.pushy.me/incident/524/ Our service has experienced high latency for periods of up to 30 minutes in the past two days. Investigation is still underway and we are attempting various solutions to prevent high latency from reoccurring. No API requests were dropped during these periods of high latency.

]]> 2018-01-19T00:39:00+00:00 Pushy API health has stabilized https://status.pushy.me/incident/523/ The API has returned to normal operational capacity.

]]> 2018-01-18T07:30:56+00:00 Pushy Website health has stabilized https://status.pushy.me/incident/522/ The Website has returned to normal operational capacity.

]]> 2018-01-18T07:30:25+00:00 Pushy Website high latency https://status.pushy.me/incident/521/ We're investigating an issue that is causing high latency in the Website.

]]> 2018-01-18T07:10:12+00:00 Pushy API high latency https://status.pushy.me/incident/520/ We're investigating an issue that is causing high latency in the API.

]]> 2018-01-18T07:08:33+00:00 Pushy API health has stabilized https://status.pushy.me/incident/519/ The API has returned to normal operational capacity.

]]> 2018-01-17T06:41:35+00:00 Pushy API high latency https://status.pushy.me/incident/518/ We're investigating an issue that is causing high latency in the API.

]]> 2018-01-17T06:21:07+00:00 Pushy Post-mortem: High API latency https://status.pushy.me/incident/517/ Over the past few days, we have been experiencing several short periods of high latency during excessive bursts of traffic. We would like to apologize for any negative effect this has had on the immediate delivery of notifications to your users.

After attempting several remediation strategies, we have been able to find a solution that appears to be working quite well. We will be closely monitoring latency over the next few days to confirm that the issue is indeed resolved.

]]> 2017-12-21T04:24:00+00:00 Pushy API health has stabilized https://status.pushy.me/incident/516/ The API has returned to normal operational capacity.

]]> 2017-12-20T21:53:33+00:00 Pushy API high latency https://status.pushy.me/incident/515/ We're investigating an issue that is causing high latency in the API.

]]> 2017-12-20T21:33:08+00:00 Pushy Website health has stabilized https://status.pushy.me/incident/514/ The Website has returned to normal operational capacity.

]]> 2017-12-20T19:29:15+00:00 Pushy API health has stabilized https://status.pushy.me/incident/513/ The API has returned to normal operational capacity.

]]> 2017-12-20T19:28:07+00:00 Pushy Website high latency https://status.pushy.me/incident/512/ We're investigating an issue that is causing high latency in the Website.

]]> 2017-12-20T19:08:30+00:00 Pushy API high latency https://status.pushy.me/incident/511/ We're investigating an issue that is causing high latency in the API.

]]> 2017-12-20T18:46:07+00:00 Pushy API health has stabilized https://status.pushy.me/incident/510/ The API has returned to normal operational capacity.

]]> 2017-12-20T16:39:15+00:00 Pushy API high latency https://status.pushy.me/incident/509/ We're investigating an issue that is causing high latency in the API.

]]> 2017-12-20T15:35:33+00:00 Pushy API health has stabilized https://status.pushy.me/incident/508/ The API has returned to normal operational capacity.

]]> 2017-12-20T15:26:36+00:00 Pushy API high latency https://status.pushy.me/incident/507/ We're investigating an issue that is causing high latency in the API.

]]> 2017-12-20T14:44:20+00:00 Pushy API health has stabilized https://status.pushy.me/incident/506/ The API has returned to normal operational capacity.

]]> 2017-12-20T14:35:57+00:00 Pushy Website health has stabilized https://status.pushy.me/incident/505/ The Website has returned to normal operational capacity.

]]> 2017-12-20T14:29:46+00:00 Pushy Website high latency https://status.pushy.me/incident/504/ We're investigating an issue that is causing high latency in the Website.

]]> 2017-12-20T14:09:30+00:00 Pushy API high latency https://status.pushy.me/incident/503/ We're investigating an issue that is causing high latency in the API.

]]> 2017-12-20T13:18:14+00:00 Pushy API health has stabilized https://status.pushy.me/incident/502/ The API has returned to normal operational capacity.

]]> 2017-12-20T12:22:49+00:00 Pushy API high latency https://status.pushy.me/incident/501/ We're investigating an issue that is causing high latency in the API.

]]> 2017-12-20T12:02:36+00:00 Pushy API health has stabilized https://status.pushy.me/incident/500/ The API has returned to normal operational capacity.

]]> 2017-12-20T08:59:20+00:00 Pushy Website health has stabilized https://status.pushy.me/incident/499/ The Website has returned to normal operational capacity.

]]> 2017-12-20T08:58:27+00:00 Pushy Website high latency https://status.pushy.me/incident/498/ We're investigating an issue that is causing high latency in the Website.

]]> 2017-12-20T08:14:17+00:00 Pushy API high latency https://status.pushy.me/incident/497/ We're investigating an issue that is causing high latency in the API.

]]> 2017-12-20T08:05:29+00:00 Pushy API health has stabilized https://status.pushy.me/incident/496/ The API has returned to normal operational capacity.

]]> 2017-12-20T07:58:11+00:00 Pushy API high latency https://status.pushy.me/incident/495/ We're investigating an issue that is causing high latency in the API.

]]> 2017-12-20T07:07:07+00:00 Pushy API health has stabilized https://status.pushy.me/incident/494/ The API has returned to normal operational capacity.

]]> 2017-12-20T07:00:22+00:00 Pushy API high latency https://status.pushy.me/incident/493/ We're investigating an issue that is causing high latency in the API.

]]> 2017-12-20T06:06:14+00:00 Pushy API health has stabilized https://status.pushy.me/incident/492/ The API has returned to normal operational capacity.

]]> 2017-12-19T10:26:07+00:00 Pushy API high latency https://status.pushy.me/incident/491/ We're investigating an issue that is causing high latency in the API.

]]> 2017-12-19T08:53:02+00:00 Pushy API health has stabilized https://status.pushy.me/incident/490/ The API has returned to normal operational capacity.

]]> 2017-12-19T08:49:57+00:00 Pushy API high latency https://status.pushy.me/incident/489/ We're investigating an issue that is causing high latency in the API.

]]> 2017-12-19T08:29:41+00:00 Pushy API health has stabilized https://status.pushy.me/incident/488/ The API has returned to normal operational capacity.

]]> 2017-12-19T08:13:28+00:00 Pushy API high latency https://status.pushy.me/incident/487/ We're investigating an issue that is causing high latency in the API.

]]> 2017-12-19T07:14:37+00:00 Pushy High API latency post-mortem https://status.pushy.me/incident/486/ We've identified the root cause for high latency and are working on applying a fix.

No API request was dropped during this time. API latency is now back to normal.

]]> 2017-12-18T16:09:00+00:00 Pushy API health has stabilized https://status.pushy.me/incident/485/ The API has returned to normal operational capacity.

]]> 2017-12-18T07:59:27+00:00 Pushy API high latency https://status.pushy.me/incident/484/ We're investigating an issue that is causing high latency in the API.

]]> 2017-12-18T07:30:17+00:00 Pushy API health has stabilized https://status.pushy.me/incident/483/ The API has returned to normal operational capacity.

]]> 2017-12-17T07:59:47+00:00 Pushy API high latency https://status.pushy.me/incident/482/ We're investigating an issue that is causing high latency in the API.

]]> 2017-12-17T07:39:30+00:00 Pushy API health has stabilized https://status.pushy.me/incident/481/ The API has returned to normal operational capacity.

]]> 2017-11-19T11:01:47+00:00 Pushy API high latency https://status.pushy.me/incident/480/ We're investigating an issue that is causing high latency in the API.

]]> 2017-11-19T10:27:34+00:00 Pushy High latency post-mortem https://status.pushy.me/incident/479/ High latency for a collective duration of approximately 1 hour was caused by an increased and sudden load on our database which was not anticipated. We have provisioned additional compute resources beyond the necessary capacity and will be closely monitoring database load to prevent this from happening again in the future.

API latency and notification delivery are now back to normal.

]]> 2017-11-03T19:26:00+00:00 Pushy API health has stabilized https://status.pushy.me/incident/478/ The API has returned to normal operational capacity.

]]> 2017-11-02T21:26:12+00:00 Pushy Website health has stabilized https://status.pushy.me/incident/477/ The Website has returned to normal operational capacity.

]]> 2017-11-02T21:25:24+00:00 Pushy Website high latency https://status.pushy.me/incident/476/ We're investigating an issue that is causing high latency in the Website.

]]> 2017-11-02T20:54:57+00:00 Pushy API high latency https://status.pushy.me/incident/475/ We're investigating an issue that is causing high latency in the API.

]]> 2017-11-02T20:52:28+00:00 Pushy API health has stabilized https://status.pushy.me/incident/474/ The API has returned to normal operational capacity.

]]> 2017-10-24T15:34:40+00:00 Pushy API high latency https://status.pushy.me/incident/473/ We're investigating an issue that is causing high latency in the API.

]]> 2017-10-24T15:14:31+00:00 Pushy High API latency post-mortem https://status.pushy.me/incident/472/ High API latency for a collective duration of approximately 10 minutes was caused by a routine database maintenance task that required more processing power than anticipated. We have taken measures to reduce the load this task places on the database to prevent this from happening again in the future.

API latency is back to normal. All API requests during this period have not been dropped or rejected.

]]> 2017-10-21T10:55:00+00:00 Pushy API health has stabilized https://status.pushy.me/incident/471/ The API has returned to normal operational capacity.

]]> 2017-10-21T10:14:10+00:00 Pushy API high latency https://status.pushy.me/incident/470/ We're investigating an issue that is causing high latency in the API.

]]> 2017-10-21T09:31:18+00:00 Pushy High API latency post-mortem https://status.pushy.me/incident/463/ High API latency for a collective duration of approximately 30 minutes was caused by a routine database maintenance task that required more processing power than anticipated. We have taken measures to reduce the load this task places on the database to prevent this from happening again in the future.

API latency is back to normal. All API requests during this period have not been dropped or rejected.

]]> 2017-09-21T16:26:00+00:00 Pushy API health has stabilized https://status.pushy.me/incident/462/ The API has returned to normal operational capacity.

]]> 2017-09-21T16:15:25+00:00 Pushy API high latency https://status.pushy.me/incident/461/ We're investigating an issue that is causing high latency in the API.

]]> 2017-09-21T15:44:29+00:00 Pushy Notification Service health has stabilized https://status.pushy.me/incident/460/ The Notification Service has returned to normal operational capacity.

]]> 2017-08-14T21:01:42+00:00 Pushy Notification Service high latency https://status.pushy.me/incident/459/ We're investigating an issue that is causing high latency in the Notification Service.

]]> 2017-08-14T20:39:42+00:00 Pushy Notification Service health has stabilized https://status.pushy.me/incident/458/ The Notification Service has returned to normal operational capacity.

]]> 2017-08-11T18:52:44+00:00 Pushy Notification Service high latency https://status.pushy.me/incident/457/ We're investigating an issue that is causing high latency in the Notification Service.

]]> 2017-08-11T18:27:29+00:00 Pushy Notification Service high latency has been resolved https://status.pushy.me/incident/456/ The Notification Service has returned to normal response latency.

The issue was caused by a single faulty server in our notification service stack which had affected the latency. We have replaced the server and latency is now normal.

]]> 2017-07-18T18:45:00+00:00 Pushy Notification Service high latency https://status.pushy.me/incident/455/ We're investigating an issue that is causing high latency in the Notification Service.

]]> 2017-07-18T18:30:29+00:00 Pushy API high latency post-mortem https://status.pushy.me/incident/454/ High API latency was caused by an unexpected burst of API requests that managed to surpass the capabilities our over-provisioned compute capacity. We have greatly increased the available API compute capacity and will be monitoring continuously to prevent a similar incident from happening in the future.

API latency is back to normal. All API requests during this period have not been dropped or rejected.

]]> 2017-05-24T12:31:00+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/453/ The API has returned to normal response latency.

]]> 2017-05-24T12:24:45+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/452/ The Website has returned to normal response latency.

]]> 2017-05-24T12:24:30+00:00 Pushy Website high latency https://status.pushy.me/incident/451/ We're investigating an issue that is causing high latency in the Website.

]]> 2017-05-24T10:23:32+00:00 Pushy API high latency https://status.pushy.me/incident/450/ We're investigating an issue that is causing high latency in the API.

]]> 2017-05-24T10:17:18+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/448/ The API has returned to normal response latency.

]]> 2017-05-23T22:47:41+00:00 Pushy API high latency post-mortem https://status.pushy.me/incident/449/ High API latency was caused by a number of inefficient indexes within the database servers. We have taken measures to automatically rebuild inefficient indexes to prevent a similar incident from happening in the future.

API latency is back to normal. All API requests during this period have not been dropped or rejected.

]]> 2017-05-23T22:44:00+00:00 Pushy API high latency update: root cause identified https://status.pushy.me/incident/447/ We have identified the underlying cause for the issue causing high API latency and are deploying a hotfix at this time. All servers should be patched within the next 30 minutes and high latency is expected to return to normal ranges. No requests were dropped or rejected as a result of this performance degradation.

]]> 2017-05-23T20:38:00+00:00 Pushy API high latency https://status.pushy.me/incident/446/ We're investigating an issue that is causing high latency in the API.

]]> 2017-05-23T16:27:36+00:00 Pushy High latency post-mortem https://status.pushy.me/incident/445/ High API / website latency was caused by an unoptimized database query within the device registration endpoint. We have thoroughly optimized the endpoint to prevent a similar event from happening again in the future.

API latency is back to normal.

]]> 2017-05-18T08:40:00+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/444/ The API has returned to normal response latency.

]]> 2017-05-18T04:45:53+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/443/ The Website has returned to normal response latency.

]]> 2017-05-18T04:42:28+00:00 Pushy Website high latency https://status.pushy.me/incident/442/ We're investigating an issue that is causing high latency in the Website.

]]> 2017-05-18T00:25:37+00:00 Pushy API high latency https://status.pushy.me/incident/441/ We're investigating an issue that is causing high latency in the API.

]]> 2017-05-17T23:02:20+00:00 Pushy High latency post-mortem https://status.pushy.me/incident/440/ High latency for a collective duration of approximately 40 minutes was caused by a bulk number of requests sent to our API during a short period of time. We have taken steps to enforce a hard limit on the number of requests that can be sent to the API on a per-account basis to prevent a similar event from happening again in the future.

API latency is back to normal.

]]> 2017-04-19T15:17:00+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/439/ The Website has returned to normal response latency.

]]> 2017-04-19T15:16:17+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/438/ The API has returned to normal response latency.

]]> 2017-04-19T15:13:50+00:00 Pushy Website high latency https://status.pushy.me/incident/437/ We're investigating an issue that is causing high latency in the Website.

]]> 2017-04-19T14:56:09+00:00 Pushy API high latency https://status.pushy.me/incident/436/ We're investigating an issue that is causing high latency in the API.

]]> 2017-04-19T14:48:21+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/435/ The API has returned to normal response latency.

]]> 2017-04-19T14:34:43+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/434/ The Website has returned to normal response latency.

]]> 2017-04-19T14:34:32+00:00 Pushy Website high latency https://status.pushy.me/incident/433/ We're investigating an issue that is causing high latency in the Website.

]]> 2017-04-19T13:51:40+00:00 Pushy API high latency https://status.pushy.me/incident/432/ We're investigating an issue that is causing high latency in the API.

]]> 2017-04-19T13:24:37+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/431/ The API has returned to normal response latency.

]]> 2017-04-19T00:40:28+00:00 Pushy API high latency https://status.pushy.me/incident/430/ We're investigating an issue that is causing high latency in the API.

]]> 2017-04-19T00:08:13+00:00 Pushy High API latency post-mortem https://status.pushy.me/incident/429/ High API latency for a collective duration of approximately 50 minutes was caused by a routine database cleanup that required more processing power than anticipated. We have taken measures to reduce the load this task places on the database to prevent this from happening again in the future.

API latency is back to normal. All API requests during this period have not been dropped or rejected.

]]> 2017-04-18T18:09:00+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/428/ The API has returned to normal response latency.

]]> 2017-04-18T17:17:35+00:00 Pushy API high latency https://status.pushy.me/incident/427/ We're investigating an issue that is causing high latency in the API.

]]> 2017-04-18T16:27:40+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/426/ The API has returned to normal response latency.

]]> 2017-04-08T00:29:10+00:00 Pushy API high latency https://status.pushy.me/incident/425/ We're investigating an issue that is causing high latency in the API.

]]> 2017-04-08T00:09:08+00:00 Pushy Notification Service high latency has been resolved https://status.pushy.me/incident/424/ The Notification Service has returned to normal response latency.

]]> 2017-04-07T16:46:01+00:00 Pushy Notification Service high latency https://status.pushy.me/incident/423/ We're investigating an issue that is causing high latency in the Notification Service.

]]> 2017-04-07T15:03:23+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/422/ The Website has returned to normal response latency.

]]> 2017-04-01T03:46:18+00:00 Pushy Website high latency https://status.pushy.me/incident/421/ We're investigating an issue that is causing high latency in the Website.

]]> 2017-04-01T03:25:36+00:00 Pushy High API latency post-mortem https://status.pushy.me/incident/420/ High API latency for a collective duration of approximately 10 minutes was caused by a memory leak in one of our Node.js packages. We believe we have been able to pinpoint the exact reason for the leak and have deployed a fix to prevent this from happening in the future.

We will continue to monitor the API servers' memory utilization to verify that the leak has been mitigated.

]]> 2017-03-13T15:06:00+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/419/ The API has returned to normal response latency.

]]> 2017-03-13T08:23:32+00:00 Pushy API high latency https://status.pushy.me/incident/418/ We're investigating an issue that is causing high latency in the API.

]]> 2017-03-13T08:03:13+00:00 Pushy API high latency post-mortem https://status.pushy.me/incident/415/ High API latency for a duration of approximately 5 minutes was caused by a burst of requests to our API which required more RAM than anticipated. No requests were dropped, API latency is back to normal ranges.

The API servers' memory has been increased substantially to prevent this from happening again in the future.

]]> 2017-03-09T11:14:00+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/414/ The API has returned to normal response latency.

]]> 2017-03-09T10:52:40+00:00 Pushy API high latency https://status.pushy.me/incident/413/ We're investigating an issue that is causing high latency in the API.

]]> 2017-03-09T10:32:20+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/412/ The API has returned to normal response latency.

]]> 2017-03-06T09:28:23+00:00 Pushy API high latency https://status.pushy.me/incident/411/ We're investigating an issue that is causing high latency in the API.

]]> 2017-03-06T08:49:10+00:00 Pushy API high latency resolved https://status.pushy.me/incident/410/ High API latency for a duration of approximately 5 minutes was caused by a routine database maintenance which required more processing power than anticipated. No requests were dropped, API latency is back to normal ranges.

]]> 2017-02-21T10:46:00+00:00 Pushy API high latency https://status.pushy.me/incident/409/ We're investigating an issue that is causing high latency in the API.

]]> 2017-02-21T10:43:22+00:00 Pushy February 19th high latency incident post-mortem https://status.pushy.me/incident/407/ We've identified and resolved the root cause of high latency: the primary database server had run out of memory.

Within a few moments of the incident, a secondary database server had taken over as the primary and started accepting read/write queries from the API. It took the secondary database a few minutes to finish processing the queued requests and lower latency back to normal ranges.

Once we made sure the secondary server was stable and latency had become tolerable again, we increased the primary server's available memory and began a full data resync, which took around 40 minutes to complete.

We will be constantly monitoring the database servers' resource utilization to prevent a similar incident from happening in the future.

]]> 2017-02-19T23:44:00+00:00 Pushy Notification Service high latency https://status.pushy.me/incident/406/ We're investigating an issue that is causing high latency in the Notification Service.

]]> 2017-02-19T23:03:09+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/405/ The API has returned to normal response latency.

]]> 2017-02-19T22:30:05+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/404/ The Website has returned to normal response latency.

]]> 2017-02-19T22:00:28+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/403/ The API has returned to normal response latency.

]]> 2017-02-19T21:55:31+00:00 Pushy We're working on resolving the high latency issues https://status.pushy.me/incident/402/ We've identified the root cause of the high latency: the primary MongoDB instance had run out of memory. We have increased its available memory, began a full resync, and will be taking steps to ensure this does not happen again in the future. The resync should complete within 15 - 25 minutes.

]]> 2017-02-19T21:36:00+00:00 Pushy Notification Service high latency https://status.pushy.me/incident/401/ We're investigating an issue that is causing high latency in the Notification Service.

]]> 2017-02-19T20:59:39+00:00 Pushy API high latency https://status.pushy.me/incident/400/ We're investigating an issue that is causing high latency in the API.

]]> 2017-02-19T20:56:45+00:00 Pushy Website high latency https://status.pushy.me/incident/399/ We're investigating an issue that is causing high latency in the Website.

]]> 2017-02-19T20:56:35+00:00 Pushy Notification Service high latency resolved https://status.pushy.me/incident/398/ Notification Service latency has been resolved. No data was lost, latency is back to normal ranges.

]]> 2017-02-08T15:53:00+00:00 Pushy Notification Service high latency https://status.pushy.me/incident/394/ We're investigating an issue that is causing high latency in the Notification Service.

]]> 2017-02-08T14:32:00+00:00 Pushy High latency fixed https://status.pushy.me/incident/392/ High API latency for a duration of approx. 7 minutes was caused by a routine database maintenance which required more processing power than anticipated. No requests were dropped, API latency is back to normal ranges.

]]> 2017-02-02T14:24:00+00:00 Pushy API high latency https://status.pushy.me/incident/391/ We're investigating an issue that is causing high latency in the API.

]]> 2017-02-02T14:13:41+00:00 Pushy Website high latency https://status.pushy.me/incident/390/ We're investigating an issue that is causing high latency in the Website.

]]> 2017-02-02T14:13:32+00:00 Pushy Dashboard health check passed https://status.pushy.me/incident/387/ The HTTP endpoint is now operating as expected.

]]> 2017-01-14T15:22:28+00:00 Pushy Dashboard health check failed https://status.pushy.me/incident/386/ We're investigating an issue that is causing the HTTP health check to fail for the Dashboard.

]]> 2017-01-14T15:08:44+00:00 Pushy Dashboard high latency has been resolved https://status.pushy.me/incident/385/ The Dashboard has returned to normal response latency.

]]> 2017-01-02T12:04:50+00:00 Pushy Dashboard high latency https://status.pushy.me/incident/384/ We're investigating an issue that is causing high latency in the Dashboard.

]]> 2017-01-02T11:33:17+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/383/ The API has returned to normal response latency.

]]> 2016-12-25T10:45:41+00:00 Pushy API high latency https://status.pushy.me/incident/382/ We're investigating an issue that is causing high latency in the API.

]]> 2016-12-25T10:25:33+00:00 Pushy Dashboard high latency has been resolved https://status.pushy.me/incident/381/ The Dashboard has returned to normal response latency.

]]> 2016-12-23T18:09:12+00:00 Pushy Dashboard high latency https://status.pushy.me/incident/380/ We're investigating an issue that is causing high latency in the Dashboard.

]]> 2016-12-23T17:53:04+00:00 Pushy Dashboard high latency has been resolved https://status.pushy.me/incident/379/ The Dashboard has returned to normal response latency.

]]> 2016-12-08T12:26:33+00:00 Pushy Dashboard high latency https://status.pushy.me/incident/378/ We're investigating an issue that is causing high latency in the Dashboard.

]]> 2016-12-08T12:10:28+00:00 Pushy API high latency core issue identified and resolved https://status.pushy.me/incident/377/ The underlying issue which caused today's high API response latency for approximately 1 hour was identified and resolved.

No downtime was incurred, but notification delivery speed may have been affected. All push notifications sent during this time have been persisted successfully.

]]> 2016-12-07T23:46:00+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/376/ The API has returned to normal response latency.

]]> 2016-12-07T23:37:36+00:00 Pushy API high latency https://status.pushy.me/incident/375/ We're investigating an issue that is causing high latency in the API.

]]> 2016-12-07T22:24:01+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/374/ The API has returned to normal response latency.

]]> 2016-10-27T08:03:16+00:00 Pushy API high latency https://status.pushy.me/incident/373/ We're investigating an issue that is causing high latency in the API.

]]> 2016-10-27T07:46:38+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/372/ The API has returned to normal response latency.

]]> 2016-10-25T08:35:52+00:00 Pushy API high latency https://status.pushy.me/incident/371/ We're investigating an issue that is causing high latency in the API.

]]> 2016-10-25T08:07:49+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/370/ The API has returned to normal response latency.

]]> 2016-10-24T08:29:54+00:00 Pushy API high latency https://status.pushy.me/incident/369/ We're investigating an issue that is causing high latency in the API.

]]> 2016-10-24T08:09:46+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/368/ The API has returned to normal response latency.

]]> 2016-10-16T23:29:19+00:00 Pushy API high latency https://status.pushy.me/incident/367/ We're investigating an issue that is causing high latency in the API.

]]> 2016-10-16T22:53:49+00:00 Pushy Dashboard high latency has been resolved https://status.pushy.me/incident/366/ The Dashboard has returned to normal response latency.

]]> 2016-10-12T11:45:12+00:00 Pushy Dashboard high latency https://status.pushy.me/incident/365/ We're investigating an issue that is causing high latency in the Dashboard.

]]> 2016-10-12T11:06:49+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/364/ The API has returned to normal response latency.

]]> 2016-10-12T09:59:33+00:00 Pushy API high latency https://status.pushy.me/incident/363/ We're investigating an issue that is causing high latency in the API.

]]> 2016-10-12T09:36:53+00:00 Pushy Dashboard high latency has been resolved https://status.pushy.me/incident/362/ The Dashboard has returned to normal response latency.

]]> 2016-10-12T09:23:09+00:00 Pushy Dashboard high latency https://status.pushy.me/incident/361/ We're investigating an issue that is causing high latency in the Dashboard.

]]> 2016-10-12T08:58:55+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/360/ The API has returned to normal response latency.

]]> 2016-10-12T08:52:21+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/359/ The Website has returned to normal response latency.

]]> 2016-10-12T08:50:13+00:00 Pushy API high latency https://status.pushy.me/incident/358/ We're investigating an issue that is causing high latency in the API.

]]> 2016-10-12T08:25:02+00:00 Pushy Website high latency https://status.pushy.me/incident/357/ We're investigating an issue that is causing high latency in the Website.

]]> 2016-10-12T08:24:57+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/356/ The API has returned to normal response latency.

]]> 2016-10-12T08:19:32+00:00 Pushy API high latency https://status.pushy.me/incident/355/ We're investigating an issue that is causing high latency in the API.

]]> 2016-10-12T08:02:54+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/354/ The API has returned to normal response latency.

]]> 2016-10-12T06:41:10+00:00 Pushy API high latency https://status.pushy.me/incident/353/ We're investigating an issue that is causing high latency in the API.

]]> 2016-10-12T06:24:01+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/352/ The API has returned to normal response latency.

]]> 2016-10-12T03:53:17+00:00 Pushy API high latency https://status.pushy.me/incident/351/ We're investigating an issue that is causing high latency in the API.

]]> 2016-10-12T03:36:14+00:00 Pushy Dashboard high latency has been resolved https://status.pushy.me/incident/350/ The Dashboard has returned to normal response latency.

]]> 2016-10-11T18:59:39+00:00 Pushy Dashboard high latency https://status.pushy.me/incident/349/ We're investigating an issue that is causing high latency in the Dashboard.

]]> 2016-10-11T18:05:14+00:00 Pushy Dashboard high latency has been resolved https://status.pushy.me/incident/348/ The Dashboard has returned to normal response latency.

]]> 2016-10-11T10:35:22+00:00 Pushy Dashboard high latency https://status.pushy.me/incident/347/ We're investigating an issue that is causing high latency in the Dashboard.

]]> 2016-10-11T09:41:07+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/346/ The API has returned to normal response latency.

]]> 2016-10-11T05:06:00+00:00 Pushy API high latency https://status.pushy.me/incident/345/ We're investigating an issue that is causing high latency in the API.

]]> 2016-10-11T04:48:57+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/344/ The API has returned to normal response latency.

]]> 2016-10-10T05:32:15+00:00 Pushy API high latency https://status.pushy.me/incident/343/ We're investigating an issue that is causing high latency in the API.

]]> 2016-10-10T05:15:25+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/342/ The API has returned to normal response latency.

]]> 2016-10-10T05:06:21+00:00 Pushy API high latency https://status.pushy.me/incident/341/ We're investigating an issue that is causing high latency in the API.

]]> 2016-10-10T04:49:19+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/340/ The API has returned to normal response latency.

]]> 2016-10-10T00:03:07+00:00 Pushy API high latency https://status.pushy.me/incident/339/ We're investigating an issue that is causing high latency in the API.

]]> 2016-10-09T23:39:54+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/338/ The API has returned to normal response latency.

]]> 2016-10-09T09:35:06+00:00 Pushy API high latency https://status.pushy.me/incident/337/ We're investigating an issue that is causing high latency in the API.

]]> 2016-10-09T09:18:05+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/336/ The Website has returned to normal response latency.

]]> 2016-10-01T03:26:20+00:00 Pushy Website high latency https://status.pushy.me/incident/335/ We're investigating an issue that is causing high latency in the Website.

]]> 2016-10-01T03:09:19+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/334/ The API has returned to normal response latency.

]]> 2016-09-29T06:10:52+00:00 Pushy API high latency https://status.pushy.me/incident/333/ We're investigating an issue that is causing high latency in the API.

]]> 2016-09-29T05:35:25+00:00 Pushy Resolved high notification delivery error rates https://status.pushy.me/incident/329/ We've found the underlying cause of an issue in the notification service that has affected a fraction of devices, causing failed delivery attempts.

Notifications to these devices have been persisted and will be delivered as soon as these devices reconnect to our network.

]]> 2016-09-23T08:37:00+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/328/ The API has returned to normal response latency.

]]> 2016-09-18T17:07:26+00:00 Pushy API high latency https://status.pushy.me/incident/327/ We're investigating an issue that is causing high latency in the API.

]]> 2016-09-18T16:49:49+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/326/ The Website has returned to normal response latency.

]]> 2016-09-18T13:25:45+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/325/ The API has returned to normal response latency.

]]> 2016-09-18T13:17:42+00:00 Pushy Website high latency https://status.pushy.me/incident/324/ We're investigating an issue that is causing high latency in the Website.

]]> 2016-09-18T13:08:03+00:00 Pushy API high latency https://status.pushy.me/incident/323/ We're investigating an issue that is causing high latency in the API.

]]> 2016-09-18T12:58:55+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/322/ The API has returned to normal response latency.

]]> 2016-09-17T19:59:34+00:00 Pushy API high latency https://status.pushy.me/incident/321/ We're investigating an issue that is causing high latency in the API.

]]> 2016-09-17T19:41:57+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/320/ The API has returned to normal response latency.

]]> 2016-09-17T19:36:32+00:00 Pushy API high latency https://status.pushy.me/incident/319/ We're investigating an issue that is causing high latency in the API.

]]> 2016-09-17T19:18:54+00:00 Pushy Maintenence complete https://status.pushy.me/incident/318/ Thank you for your patience.

]]> 2016-09-17T19:14:50+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/317/ The API has returned to normal response latency.

]]> 2016-09-17T19:12:26+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/316/ The Website has returned to normal response latency.

]]> 2016-09-17T19:08:39+00:00 Pushy Notification Service high latency has been resolved https://status.pushy.me/incident/315/ The Notification Service has returned to normal response latency.

]]> 2016-09-17T19:04:52+00:00 Pushy Website high latency https://status.pushy.me/incident/314/ We're investigating an issue that is causing high latency in the Website.

]]> 2016-09-17T18:50:58+00:00 Pushy API high latency https://status.pushy.me/incident/313/ We're investigating an issue that is causing high latency in the API.

]]> 2016-09-17T18:48:45+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/312/ The Website has returned to normal response latency.

]]> 2016-09-17T18:48:40+00:00 Pushy Notification Service high latency https://status.pushy.me/incident/311/ We're investigating an issue that is causing high latency in the Notification Service.

]]> 2016-09-17T18:47:01+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/310/ The API has returned to normal response latency.

]]> 2016-09-17T18:45:51+00:00 Pushy Notification Service high latency has been resolved https://status.pushy.me/incident/309/ The Notification Service has returned to normal response latency.

]]> 2016-09-17T18:41:30+00:00 Pushy Website high latency https://status.pushy.me/incident/308/ We're investigating an issue that is causing high latency in the Website.

]]> 2016-09-17T18:30:46+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/307/ The Website has returned to normal response latency.

]]> 2016-09-17T18:26:58+00:00 Pushy Notification Service high latency https://status.pushy.me/incident/306/ We're investigating an issue that is causing high latency in the Notification Service.

]]> 2016-09-17T18:23:43+00:00 Pushy Website high latency https://status.pushy.me/incident/305/ We're investigating an issue that is causing high latency in the Website.

]]> 2016-09-17T18:09:17+00:00 Pushy Notification Service high latency has been resolved https://status.pushy.me/incident/304/ The Notification Service has returned to normal response latency.

]]> 2016-09-17T18:04:56+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/303/ The Website has returned to normal response latency.

]]> 2016-09-17T17:48:53+00:00 Pushy Notification Service high latency https://status.pushy.me/incident/302/ We're investigating an issue that is causing high latency in the Notification Service.

]]> 2016-09-17T17:47:13+00:00 Pushy API high latency https://status.pushy.me/incident/301/ We're investigating an issue that is causing high latency in the API.

]]> 2016-09-17T17:47:06+00:00 Pushy Notification Service high latency has been resolved https://status.pushy.me/incident/300/ The Notification Service has returned to normal response latency.

]]> 2016-09-17T17:46:29+00:00 Pushy API health check passed https://status.pushy.me/incident/299/ The HTTP endpoint is now operating as expected.

]]> 2016-09-17T17:45:04+00:00 Pushy Website high latency https://status.pushy.me/incident/298/ We're investigating an issue that is causing high latency in the Website.

]]> 2016-09-17T17:30:59+00:00 Pushy Notification Service high latency https://status.pushy.me/incident/297/ We're investigating an issue that is causing high latency in the Notification Service.

]]> 2016-09-17T17:28:47+00:00 Pushy API health check failed https://status.pushy.me/incident/296/ We're investigating an issue that is causing the HTTP health check to fail for the API.

]]> 2016-09-17T17:27:29+00:00 Pushy Core database migration scheduled https://status.pushy.me/incident/295/ We are migrating our replicated database to another service provider to improve overall uptime and performance. There should be no downtime during the migration.

]]> 2016-09-17T14:54:10+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/294/ The API has returned to normal response latency.

]]> 2016-09-16T09:59:27+00:00 Pushy API high latency https://status.pushy.me/incident/293/ We're investigating an issue that is causing high latency in the API.

]]> 2016-09-16T09:41:50+00:00 Pushy API health check passed https://status.pushy.me/incident/292/ The HTTP endpoint is now operating as expected.

]]> 2016-09-16T05:21:35+00:00 Pushy API health check failed https://status.pushy.me/incident/291/ We're investigating an issue that is causing the HTTP health check to fail for the API.

]]> 2016-09-16T05:03:36+00:00 Pushy Notification Service health check passed https://status.pushy.me/incident/290/ The HTTP endpoint is now operating as expected.

]]> 2016-09-15T21:27:31+00:00 Pushy Notification Service health check failed https://status.pushy.me/incident/289/ We're investigating an issue that is causing the HTTP health check to fail for the Notification Service.

]]> 2016-09-15T21:10:00+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/288/ The API has returned to normal response latency.

]]> 2016-09-15T09:24:46+00:00 Pushy Service performance issues fixed https://status.pushy.me/incident/232/ The Notification Service and API latency has returned to normal, and all other service performance issues have been fixed.

]]> 2016-09-15T09:03:00+00:00 Pushy Service performance issues https://status.pushy.me/incident/231/ We're investigating an issue that is causing high latency in the Notification Service & API.

]]> 2016-09-14T21:46:00+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/230/ The API has returned to normal response latency.

]]> 2016-09-13T17:19:54+00:00 Pushy API high latency https://status.pushy.me/incident/229/ We're investigating an issue that is causing high latency in the API.

]]> 2016-09-13T17:02:11+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/228/ The API has returned to normal response latency.

]]> 2016-09-13T16:58:51+00:00 Pushy API high latency https://status.pushy.me/incident/227/ We're investigating an issue that is causing high latency in the API.

]]> 2016-09-13T16:41:08+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/226/ The API has returned to normal response latency.

]]> 2016-09-05T19:05:14+00:00 Pushy API high latency https://status.pushy.me/incident/225/ We're investigating an issue that is causing high latency in the API.

]]> 2016-09-05T18:47:02+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/224/ The API has returned to normal response latency.

]]> 2016-09-05T18:43:13+00:00 Pushy API high latency https://status.pushy.me/incident/223/ We're investigating an issue that is causing high latency in the API.

]]> 2016-09-05T18:25:01+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/222/ The API has returned to normal response latency.

]]> 2016-09-05T06:14:35+00:00 Pushy API high latency https://status.pushy.me/incident/221/ We're investigating an issue that is causing high latency in the API.

]]> 2016-09-05T05:56:21+00:00 Pushy Website health check passed https://status.pushy.me/incident/220/ The HTTP endpoint is now operating as expected.

]]> 2016-09-01T14:29:51+00:00 Pushy Website health check failed https://status.pushy.me/incident/219/ We're investigating an issue that is causing the HTTP health check to fail for the Website.

]]> 2016-09-01T14:11:54+00:00 Pushy Notification Service health check passed https://status.pushy.me/incident/218/ The HTTP endpoint is now operating as expected.

]]> 2016-08-31T04:06:06+00:00 Pushy Notification Service health check failed https://status.pushy.me/incident/217/ We're investigating an issue that is causing the HTTP health check to fail for the Notification Service.

]]> 2016-08-31T03:48:03+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/216/ The Website has returned to normal response latency.

]]> 2016-08-28T22:35:16+00:00 Pushy Website high latency https://status.pushy.me/incident/215/ We're investigating an issue that is causing high latency in the Website.

]]> 2016-08-28T20:38:35+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/214/ The API has returned to normal response latency.

]]> 2016-08-28T15:44:52+00:00 Pushy API high latency https://status.pushy.me/incident/213/ We're investigating an issue that is causing high latency in the API.

]]> 2016-08-28T15:26:39+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/212/ The API has returned to normal response latency.

]]> 2016-08-28T15:21:14+00:00 Pushy API high latency https://status.pushy.me/incident/211/ We're investigating an issue that is causing high latency in the API.

]]> 2016-08-28T14:52:23+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/210/ The API has returned to normal response latency.

]]> 2016-08-28T08:17:40+00:00 Pushy API high latency https://status.pushy.me/incident/209/ We're investigating an issue that is causing high latency in the API.

]]> 2016-08-28T07:59:28+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/208/ The API has returned to normal response latency.

]]> 2016-08-27T09:04:38+00:00 Pushy API high latency https://status.pushy.me/incident/207/ We're investigating an issue that is causing high latency in the API.

]]> 2016-08-27T08:46:24+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/206/ The API has returned to normal response latency.

]]> 2016-08-23T11:21:41+00:00 Pushy API high latency https://status.pushy.me/incident/205/ We're investigating an issue that is causing high latency in the API.

]]> 2016-08-23T11:03:29+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/204/ The API has returned to normal response latency.

]]> 2016-08-21T14:14:15+00:00 Pushy API high latency https://status.pushy.me/incident/203/ We're investigating an issue that is causing high latency in the API.

]]> 2016-08-21T13:55:31+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/202/ The Website has returned to normal response latency.

]]> 2016-08-21T12:45:40+00:00 Pushy Website high latency https://status.pushy.me/incident/201/ We're investigating an issue that is causing high latency in the Website.

]]> 2016-08-21T12:26:56+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/200/ The API has returned to normal response latency.

]]> 2016-08-21T11:46:23+00:00 Pushy API high latency https://status.pushy.me/incident/199/ We're investigating an issue that is causing high latency in the API.

]]> 2016-08-21T11:27:38+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/198/ The Website has returned to normal response latency.

]]> 2016-08-19T17:29:28+00:00 Pushy Website high latency https://status.pushy.me/incident/197/ We're investigating an issue that is causing high latency in the Website.

]]> 2016-08-19T17:10:42+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/196/ The API has returned to normal response latency.

]]> 2016-08-18T11:45:35+00:00 Pushy API high latency https://status.pushy.me/incident/195/ We're investigating an issue that is causing high latency in the API.

]]> 2016-08-18T11:26:52+00:00 Pushy Dashboard high latency has been resolved https://status.pushy.me/incident/194/ The Dashboard has returned to normal response latency.

]]> 2016-08-18T10:15:21+00:00 Pushy Dashboard high latency https://status.pushy.me/incident/193/ We're investigating an issue that is causing high latency in the Dashboard.

]]> 2016-08-18T09:56:38+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/192/ The API has returned to normal response latency.

]]> 2016-08-18T06:22:30+00:00 Pushy API high latency https://status.pushy.me/incident/191/ We're investigating an issue that is causing high latency in the API.

]]> 2016-08-18T06:03:43+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/190/ The API has returned to normal response latency.

]]> 2016-08-17T02:48:34+00:00 Pushy API high latency https://status.pushy.me/incident/189/ We're investigating an issue that is causing high latency in the API.

]]> 2016-08-17T02:29:48+00:00 Pushy Dashboard high latency has been resolved https://status.pushy.me/incident/188/ The Dashboard has returned to normal response latency.

]]> 2016-08-16T10:53:24+00:00 Pushy Dashboard high latency https://status.pushy.me/incident/187/ We're investigating an issue that is causing high latency in the Dashboard.

]]> 2016-08-16T10:34:43+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/186/ The Website has returned to normal response latency.

]]> 2016-08-06T17:29:36+00:00 Pushy Website high latency https://status.pushy.me/incident/185/ We're investigating an issue that is causing high latency in the Website.

]]> 2016-08-06T17:10:36+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/184/ The Website has returned to normal response latency.

]]> 2016-08-06T17:07:47+00:00 Pushy Website high latency https://status.pushy.me/incident/183/ We're investigating an issue that is causing high latency in the Website.

]]> 2016-08-06T16:09:34+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/182/ The Website has returned to normal response latency.

]]> 2016-08-06T16:06:49+00:00 Pushy Website high latency https://status.pushy.me/incident/181/ We're investigating an issue that is causing high latency in the Website.

]]> 2016-08-06T15:16:35+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/180/ The Website has returned to normal response latency.

]]> 2016-08-06T15:13:48+00:00 Pushy Website high latency https://status.pushy.me/incident/179/ We're investigating an issue that is causing high latency in the Website.

]]> 2016-08-06T14:17:39+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/178/ The Website has returned to normal response latency.

]]> 2016-08-06T14:14:53+00:00 Pushy Website high latency https://status.pushy.me/incident/177/ We're investigating an issue that is causing high latency in the Website.

]]> 2016-08-06T13:21:34+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/176/ The Website has returned to normal response latency.

]]> 2016-08-06T13:18:49+00:00 Pushy Website high latency https://status.pushy.me/incident/175/ We're investigating an issue that is causing high latency in the Website.

]]> 2016-08-06T12:50:30+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/174/ The Website has returned to normal response latency.

]]> 2016-08-06T12:47:44+00:00 Pushy Website high latency https://status.pushy.me/incident/173/ We're investigating an issue that is causing high latency in the Website.

]]> 2016-08-06T12:25:48+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/172/ The Website has returned to normal response latency.

]]> 2016-08-06T12:23:03+00:00 Pushy Website high latency https://status.pushy.me/incident/171/ We're investigating an issue that is causing high latency in the Website.

]]> 2016-08-06T11:26:32+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/170/ The Website has returned to normal response latency.

]]> 2016-08-06T11:23:46+00:00 Pushy Website high latency https://status.pushy.me/incident/169/ We're investigating an issue that is causing high latency in the Website.

]]> 2016-08-06T10:55:21+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/168/ The Website has returned to normal response latency.

]]> 2016-08-06T10:52:04+00:00 Pushy Website high latency https://status.pushy.me/incident/167/ We're investigating an issue that is causing high latency in the Website.

]]> 2016-08-06T10:16:18+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/166/ The Website has returned to normal response latency.

]]> 2016-08-06T10:14:36+00:00 Pushy Website high latency https://status.pushy.me/incident/165/ We're investigating an issue that is causing high latency in the Website.

]]> 2016-08-06T09:55:21+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/164/ The Website has returned to normal response latency.

]]> 2016-08-06T09:50:58+00:00 Pushy Website high latency https://status.pushy.me/incident/163/ We're investigating an issue that is causing high latency in the Website.

]]> 2016-08-06T09:30:36+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/162/ The Website has returned to normal response latency.

]]> 2016-08-06T09:27:48+00:00 Pushy Website high latency https://status.pushy.me/incident/161/ We're investigating an issue that is causing high latency in the Website.

]]> 2016-08-06T09:04:48+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/160/ The Website has returned to normal response latency.

]]> 2016-08-06T09:02:00+00:00 Pushy Website high latency https://status.pushy.me/incident/159/ We're investigating an issue that is causing high latency in the Website.

]]> 2016-08-06T08:18:44+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/158/ The Website has returned to normal response latency.

]]> 2016-08-06T08:15:57+00:00 Pushy Website high latency https://status.pushy.me/incident/157/ We're investigating an issue that is causing high latency in the Website.

]]> 2016-08-06T07:57:10+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/156/ The Website has returned to normal response latency.

]]> 2016-08-06T07:53:51+00:00 Pushy Website high latency https://status.pushy.me/incident/155/ We're investigating an issue that is causing high latency in the Website.

]]> 2016-08-06T07:28:06+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/154/ The Website has returned to normal response latency.

]]> 2016-08-06T07:27:27+00:00 Pushy Website high latency https://status.pushy.me/incident/153/ We're investigating an issue that is causing high latency in the Website.

]]> 2016-08-06T07:08:34+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/152/ The Website has returned to normal response latency.

]]> 2016-08-06T07:05:46+00:00 Pushy Website high latency https://status.pushy.me/incident/151/ We're investigating an issue that is causing high latency in the Website.

]]> 2016-08-06T06:32:39+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/150/ The Website has returned to normal response latency.

]]> 2016-08-06T06:29:51+00:00 Pushy Website high latency https://status.pushy.me/incident/149/ We're investigating an issue that is causing high latency in the Website.

]]> 2016-08-06T05:14:34+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/148/ The Website has returned to normal response latency.

]]> 2016-08-06T05:11:47+00:00 Pushy Website high latency https://status.pushy.me/incident/147/ We're investigating an issue that is causing high latency in the Website.

]]> 2016-08-06T04:25:47+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/146/ The Website has returned to normal response latency.

]]> 2016-08-06T04:23:00+00:00 Pushy Website high latency https://status.pushy.me/incident/145/ We're investigating an issue that is causing high latency in the Website.

]]> 2016-08-06T03:30:44+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/144/ The Website has returned to normal response latency.

]]> 2016-08-06T03:27:57+00:00 Pushy Website high latency https://status.pushy.me/incident/143/ We're investigating an issue that is causing high latency in the Website.

]]> 2016-08-06T03:08:39+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/142/ The Website has returned to normal response latency.

]]> 2016-08-06T03:05:51+00:00 Pushy Website high latency https://status.pushy.me/incident/141/ We're investigating an issue that is causing high latency in the Website.

]]> 2016-08-06T02:41:11+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/140/ The Website has returned to normal response latency.

]]> 2016-08-06T02:36:48+00:00 Pushy Website high latency https://status.pushy.me/incident/139/ We're investigating an issue that is causing high latency in the Website.

]]> 2016-08-06T02:15:51+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/138/ The Website has returned to normal response latency.

]]> 2016-08-06T02:13:05+00:00 Pushy Website high latency https://status.pushy.me/incident/137/ We're investigating an issue that is causing high latency in the Website.

]]> 2016-08-06T01:49:00+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/136/ The Website has returned to normal response latency.

]]> 2016-08-06T01:43:01+00:00 Pushy Website high latency https://status.pushy.me/incident/135/ We're investigating an issue that is causing high latency in the Website.

]]> 2016-08-06T01:19:28+00:00 Pushy API high latency has been resolved https://status.pushy.me/incident/134/ The API has returned to normal response latency.

]]> 2016-08-03T14:21:20+00:00 Pushy API high latency https://status.pushy.me/incident/133/ We're investigating an issue that is causing high latency in the API.

]]> 2016-08-03T14:02:04+00:00 Pushy Notification Service high latency has been resolved https://status.pushy.me/incident/132/ The Notification Service has returned to normal response latency.

]]> 2016-07-26T04:23:09+00:00 Pushy Notification Service high latency https://status.pushy.me/incident/131/ We're investigating an issue that is causing high latency in the Notification Service.

]]> 2016-07-26T04:12:28+00:00 Pushy High latency for a period of approximately 2 hours https://status.pushy.me/incident/118/ Our replicated database experienced high latency for a period of approximately 2 hours which caused high API response latency as well as high notification delivery speeds.

The latency was caused by a sudden burst of traffic over a short period of time.

The underlying issue has been rectified, and we have taken steps to prevent this kind of situation in the future.

]]> 2016-07-25T18:15:00+00:00 Pushy Dashboard health check passed https://status.pushy.me/incident/75/ The HTTP endpoint is now operating as expected.

]]> 2016-07-22T15:21:47+00:00 Pushy Dashboard health check failed https://status.pushy.me/incident/74/ We're investigating an issue that is causing the HTTP health check to fail for the Dashboard.

]]> 2016-07-22T15:19:39+00:00 Pushy Website high latency has been resolved https://status.pushy.me/incident/73/ The Website has returned to normal response latency.

]]> 2016-07-21T15:18:45+00:00 Pushy Website high latency https://status.pushy.me/incident/72/ We're investigating an issue that is causing high latency in the Website.

]]> 2016-07-21T15:17:38+00:00 Pushy Website health check passed https://status.pushy.me/incident/71/ The HTTP endpoint is now operating as expected.

]]> 2016-07-21T15:17:29+00:00 Pushy Website health check failed https://status.pushy.me/incident/70/ We're investigating an issue that is causing the HTTP health check to fail for the Website.

]]> 2016-07-21T15:15:35+00:00 Pushy Fixed high latency in API https://status.pushy.me/incident/17/ We've found and resolved an issue that resulted in high API latency for a duration of approximately 10 minutes.

]]> 2016-07-06T07:20:00+00:00 Pushy High latency in api.pushy.me https://status.pushy.me/incident/16/ We're investigating an issue that is causing high API latency.

]]> 2016-07-06T07:15:00+00:00 Pushy Fixed push notification high latency https://status.pushy.me/incident/15/ We have identified and resolved the high latency issue affecting notification delivery speeds.

]]> 2016-06-30T14:25:00+00:00 Pushy High latency in push notification delivery https://status.pushy.me/incident/14/ We are investigating performance issues which may be increasing the time it takes to deliver push notifications to certain devices.

]]> 2016-06-30T14:03:00+00:00 Pushy DB failover testing and reliability improvements https://status.pushy.me/incident/13/ In an effort to improve the reliability of our replicated database, we will be performing server maintenance which may affect the latency of our API. This maintenance should last no more than 1 hour and we do not expect any downtime.

Update: The maintenance is complete.

]]> 2016-06-28T19:35:00+00:00 Pushy High API latency https://status.pushy.me/incident/1/ We've found and resolved an issue that resulted in high API latency for a duration of approximately 4 minutes.

]]> 2016-06-15T18:14:00+00:00