What is this site?

We continuously monitor the status of opsgenie.com and all its related services. If there are any interruptions in service, we will post status updates here. You can also follow us on Twitter for these updates. If you are experiencing problems connecting to OpsGenie and don't see any service interruptions here, please email support@opsgenie.com or click on the blue chat bubble to chat with one of our support engineers.

  • May 07, 2018
    • 04:03 UTC Reports page is under maintenance

      ACTIVITY

      • Resolved - Reports page maintenance ended May 07, 2018, 05:00 UTC

      • Created - Reporting metrics are still being collected, reporting page not showing metrics, all other systems are running as expected. May 07, 2018, 04:03 UTC

  • May 07, 2018
    • 14:14 UTC Increased error rates at v2 API

      ACTIVITY

      • Resolved - New servers added immediately. Erroneous code rolled back. May 07, 2018, 14:26 UTC

      • Created - Latest update to the production systems caused some API servers to crash. 5xx error rates increased. May 07, 2018, 14:14 UTC

  • Mar 21, 2018
    • 18:00 UTC Logs between March 21 08:00 UTC - 17:00 UTC not searchable on Logs page

      ACTIVITY

      • Resolved - Problem solved and everything is back to normal as expected. Mar 21, 2018, 18:00 UTC

      • Created - During a migration in Logs Service, logs between March 21 08:00 UTC - 17:00 UTC not indexed.Only logs page is impacted, alert logs are fully functional during the time. Please refer to Alert Logs page for log needs. Logs exists in the log archives, if there is any critical need for logs beyond Alert Logs page please contact Customer Success team. OpsGenie working for a new logs page solution in the meantime. Mar 21, 2018, 18:00 UTC

  • Mar 16, 2018
    • 15:45 UTC Undelivered push notifications on a few number of Android devices

      ACTIVITY

      • Resolved - We've been monitoring fail ratio of push notification deliveries for Android devices. Affected users decreased over time. In the meantime, we've successfully migrated from Google Cloud Messaging (GCM) to Firebase Cloud Messaging (FCM) that is much more reliable and scalable, also recommended from Google. Now, Android push notification error rates are even lower than before. May 14, 2018, 06:00 UTC

      • Monitoring - We’re experiencing an issue with sending push notifications to a small number of Android devices due to a communication problem between Google Cloud Messaging platform (GCM) and these mobile devices. You may receive an email from us saying that your mobile contact method has been disabled which would indicate this problem. We strongly recommend all of our Android users to login to OpsGenie Android Application at least once to trigger updates of push tokens on OpsGenie which will make sure that you are not affected by this issue. In the meantime, we will continue to communicate the issue with GCM Support, and will keep you updated on the progress. Mar 16, 2018, 15:45 UTC

  • Mar 11, 2018
    • 02:12 UTC Increased error rate on voice calls and incoming call integration

      ACTIVITY

      • Resolved - All systems are operational now. Mar 11, 2018, 02:45 UTC

      • Updated - We switched voice notifications to another communication provider and error rate is 0% now. Incoming call integration is still affected. Mar 11, 2018, 02:26 UTC

      • Created - We’re experiencing an increased error rate on voice calls and incoming call integration due to a major outage on one of our communication providers. Mar 11, 2018, 02:12 UTC

  • Feb 21, 2018
    • 17:50 UTC 502 Bad Gateway errors at OpsGenie Web application

      ACTIVITY

      • Resolved - The problem is fully resolved now. Everything is functional. Feb 21, 2018, 18:10 UTC

      • Updated - Web applications are stable now. Vertically scaling applications to prevent a similar case. Feb 21, 2018, 18:05 UTC

      • Updated - There are some transactions that consume excessive resource. Starting to scale-up web applications. Feb 21, 2018, 18:00 UTC

      • Created - 502 Bad Gateway errors at OpsGenie Web application Feb 21, 2018, 17:50 UTC

  • Feb 21, 2018
    • 15:35 UTC API v1 outage and degraded performance on outgoing integrations

      ACTIVITY

      • Created - We are experiencing long transactions in the backend. Investigating the root cause. Feb 21, 2018, 15:35 UTC

      • Updated - Latest update to the production caused timeouts in the cache layer Feb 21, 2018, 17:10 UTC

      • Resolved - Update is rolled back. Everything is functional. Feb 21, 2018, 17:25 UTC

      • Updated - We sent an library upgrade to backend services at 14:44 UTC, during blue-green deploy phase everything seemed OK. When we shut down old instances transaction durations started to increase. We understood that the problem was in the caching layer. Revert decision made at 15:45 UTC, but a bug in deployment automation prevented us to solve the problem immediately. We started to revert instances manually. Between 16:28 UTC and 16:42 UTC backend services receiving API v1 requests, fully went down. Also we experienced delays at outgoing integrations up to 20 minutes. API v2 and alerting / notification flows were functional during the incident. A detailed post-mortem will be published later on. Feb 22, 2018, 12:35 UTC

  • Feb 09, 2018
    • 06:55 UTC Experiencing Network Issues

      ACTIVITY

      • Created - We are experiencing network issues. Investigating the root cause. Feb 09, 2018, 06:55 UTC

      • Updated - Request traffic is redirected to the healthy availability zones. Minority of the requests are affected due to the network issues. Feb 09, 2018, 06:57 UTC

      • Resolved - Underlying problem has been resolved. Everything is functional. Feb 09, 2018, 07:02 UTC

  • Feb 07, 2018
    • 16:17 UTC Log Service Has Delays

      ACTIVITY

      • Created - Logs were delayed for a brief amount of time. No log data will be lost during this interval. All other features, alerts & notifications working as expected. Feb 07, 2018, 16:17 UTC

      • Updated - Problem resolved. Delayed logs will be synced soon. Feb 07, 2018, 17:26 UTC

      • Resolved - No more delays in logs page. Feb 07, 2018, 23:25 UTC

  • Jan 21, 2018
    • 10:42 UTC Number of requests failing for search actions

      ACTIVITY

      • Created - There is a latency while responding to search queries for alert and user searches. Jan 21, 2018, 10:42 UTC

      • Resolved - Long running search actions have caused minor failures for 5 minutes. Jan 21, 2018, 10:47 UTC

  • Jan 19, 2018
    • 20:12 UTC Mobile Applications outage since 20:12 UTC for 10 minutes

      ACTIVITY

      • Resolved - Increased memory of the applications handling mobile application requests. Root cause analysis is in progress. Jan 19, 2018, 20:22 UTC

      • Created - There is a memory problem causing requests coming from mobile applications to fail. Jan 19, 2018, 20:12 UTC

  • Jan 18, 2018
    • 15:50 UTC Web Application & Search Service Api Requests Failing

      ACTIVITY

      • Resolved - Web application & search api endpoints back to normal, we are working on identifying the root cause and introduce improvements. Jan 18, 2018, 15:55 UTC

      • Created - During a maintenance of multiple search service clusters, search cluster availability information mistakenly assumed that all clusters are down, we immediately rolled back the change caused this. All search clusters are active. Jan 18, 2018, 15:50 UTC

  • Dec 14, 2017
    • 03:10 UTC Voice notification delivery failures to some USA numbers

      ACTIVITY

      • Resolved - OpsGenie will be sending voice notifications also from +1 (256) 568-608[0-9] , Please refer to OpsGenie vCard https://s3-us-west-2.amazonaws.com/opsgeniedownloads/voice-sms-notifications/OpsGenie_vCard.vcf Dec 14, 2017, 17:20 UTC

      • Updated - Voice notification provider switch is being performed for the numbers seen as busy by notification provider. Dec 14, 2017, 03:10 UTC

      • Created - One of our notification providers was responding with phone number busy status for voice notifications, since busy status was not a mean of direct failure, detection of the issue took more than usual. Dec 14, 2017, 03:10 UTC

  • Nov 22, 2017
    • 15:00 UTC Log Service Has Delays

      ACTIVITY

      • Resolved - Problem fully resolved, we have actively monitored all impact during the incident. Nov 23, 2017, 07:55 UTC

      • Updated - Problem resolved. Delayed logs will be synced soon. Nov 23, 2017, 07:25 UTC

      • Created - Logs were delayed for a brief amount of time. No log data will be lost during this interval. All other features, alerts & notifications working as expected. Nov 22, 2017, 15:00 UTC

  • Oct 26, 2017
    • 18:15 UTC Increased Error Rates on API

      ACTIVITY

      • Updated - Incident Post-Mortem: Summary: Our availability monitoring systems has warned many people in parallel that api.opsgenie.com had high error rates, the team had worked in parallel to find out the root cause. The root cause was an update by AWS to AWS managed services. Progress: OpsGenie has multiple layers of security & availability, we checked the availability of worldwide pop locations, load balancers and our backend applications. We found out that everything except load balancer layer was working fine, the error response from load balancers was empty delaying us to find out the actual root cause. We analyzed further in detail and finally came to the conclusion that the web application firewall layer in front of load balancer might had a problem, we disabled the firewall and api was back. Disabling of the firewall of load balancers does not introduce a direct security problem in OpsGenie stack, because we have additional firewall capabilities on pop locations. In the meantime we also considered to switch OpsGenie to the disaster recovery region, but all systems except the api layer was working well, web application with a similar technology stack was also working as expected, it was a tough decision whether to switch forth or stay and fix. Deploying a fresh load balancer in parallel was also in progress. Response of AWS: OpsGenie is hosted on AWS, heavily adopting AWS services, AWS teams done their own analysis and they found out the root cause, the AWS load balancer was left with an old version by AWS, and AWS rotated the internal verification trust between AWS Load Balancers and AWS Web Application Firewall. The old versioned Load Balancer by AWS did not receive the trust update and requests started to fail. Improvements to OpsGenie Road Map: We will be fine tuning incident processes regarding web application firewall related problems. We will be improving our automated monitoring to detect firewall related problems. Feature Requests to AWS Services: The ALB error responses shall return a clear response that the root cause is identified as fast as possible. Trust rotations or service version updates should check the compatibility between related service versions. Ability to see service versions, ability to get notified regarding critical service updates. Oct 26, 2017, 21:30 UTC

      • Resolved - We performed an update on the application firewall layer and the problem is resolved. We’re investigating the root cause. Oct 26, 2017, 18:35 UTC

      • Created - Error rate is significantly increased on API layer. We’re investigating the root cause. Oct 26, 2017, 18:15 UTC

  • Oct 18, 2017
    • 20:45 UTC Very few number of api requests timing out since 20:45 UTC

      ACTIVITY

      • Resolved - Problem fully resolved, we have actively monitored all impact during incident. Oct 18, 2017, 21:33 UTC

      • Created - Very few number of api requests are timing out because of AWS Oregon Region internet connectivity latencies, analysis in progress, all systems are working as expected. Oct 18, 2017, 20:50 UTC

  • Sep 20, 2017
    • 21:10 UTC Team dashboard not showing integrations

      ACTIVITY

      • Resolved - Fix rolled out, team dashboard integrations working as expected. Sep 20, 2017, 21:10 UTC

      • Created - Team dashboard not showing integrations, engineering team working for a fast fix. Integrations page working as expected Sep 20, 2017, 21:10 UTC

  • Sep 05, 2017
    • 03:15 UTC Problem with API & Web applications, number of requests are failing since 03:05 UTC. Investigating the problem.

      ACTIVITY

      • Updated - Fixes rolled out, last week & today, to reduce impact of cpu spikes on alert search backend, to completely remove the impact on other unrelated services Sep 12, 2017, 07:00 UTC

      • Updated - Root cause identified, a fix will be rolled out within a couple days. Sep 05, 2017, 15:00 UTC

      • Updated - Alerts page list data have inconsistencies fully resolved. Sep 05, 2017, 11:30 UTC

      • Updated - Alerts page list data have inconsistencies for minority of alerts, data consistency tool started recovering. Alert details & notifications flow working as expected. Sep 05, 2017, 08:00 UTC

      • Resolved - API back to normal, errors fully resolved. Root cause analysis is in progress. Sep 05, 2017, 03:50 UTC

      • Created - Unexpected cpu spike in all alert search backend service causing delays in API & Web applications, leading to timeouts in alert search & other api endpoints. Sep 05, 2017, 03:30 UTC

  • Aug 23, 2017
    • 17:10 UTC Minority of the alert notifications are getting delayed

      ACTIVITY

      • Resolved - All delayed notifications (3.12% of the notifications for this period) delivered successfully. Aug 23, 2017, 17:30 UTC

      • Updated - Deployment problem has been resolved. Delayed notifications will be sent. Aug 23, 2017, 17:20 UTC

      • Created - We encountered a deployment problem while releasing an infrastructural update and some alert notifications are started to be sent with delay. Aug 23, 2017, 17:10 UTC

  • Jul 21, 2017
    • 09:30 UTC Problem with the API layer detected. Number of requests are timing out since 09:20 UTC. Investigating the problem.

      ACTIVITY

      • Updated - We will be working on separating api service resources immediately, so that each service has its own resources. We will also be working to identify spike in Alert Search service. Jul 21, 2017, 12:15 UTC

      • Resolved - API back to normal, time outs fully resolved. Root cause analysis is in progress. Jul 21, 2017, 10:15 UTC

      • Updated - Number of request timing out dropped back to minor. Jul 21, 2017, 09:35 UTC

      • Created - Unexpected cpu spike in all alert search backend service causing delays in API layer, leading to timeouts in alert search & other api endpoints. Jul 21, 2017, 09:30 UTC

  • Jul 07, 2017
    • 19:40 UTC Problem with the API layer detected. Number of requests are timing out. Additional capacity have been deployed. Investigating the problem.

      ACTIVITY

      • Resolved - Api back to normal, we are investigating the root cause and working for improvements. Jul 07, 2017, 19:50 UTC

      • Created - We got an unexpected amount of spike in api layer & provisioned additional capacity urgently. Jul 07, 2017, 19:40 UTC

  • May 31, 2017
    • 13:12 UTC Delays in processing integration events

      ACTIVITY

      • Resolved - Processing back no normal, bottleneck has been identified and repaired, delays has been up to 15 minutes for some of integration events. Started process for improvements to prevent the issue happen again. May 31, 2017, 13:50 UTC

      • Updated - Delays started again, and raised up to 3 minutes, adding more capacity and trying to find out the bottleneck. May 31, 2017, 13:30 UTC

      • Updated - Processing capacity is doubled, delays are minimized May 31, 2017, 13:26 UTC

      • Created - We detected minor delay in integration event processing, started to increase processing capacity, all other services alerting & notifications working as expected. May 31, 2017, 13:12 UTC

  • May 24, 2017
    • 05:00 UTC Reports page is under maintenance, upgrade in progress

      ACTIVITY

      • Resolved - Reports page maintenance ended May 24, 2017, 07:58 UTC

      • Created - Reporting metrics are still being collected, reporting page not showing metrics, all other systems are running as expected. Expected maintenance end time is 07:00 UTC May 24, 2017, 05:00 UTC

  • May 10, 2017
    • 06:45 UTC Delays in Email Integration processing

      ACTIVITY

      • Resolved - A configuration update has caused delays in incoming email processing around 15 minutes, we immediately rolled back the configuration change, emails will be processed in the next retry at most within 10 minutes, all other integrations working normally. May 10, 2017, 06:45 UTC

  • Feb 27, 2017
    • 16:30 UTC OpsGenie Teams page was not accessible for 15 minutes

      ACTIVITY

      • Resolved - The bug was introduced in the latest hotfix. Issue is resolved Feb 27, 2017, 16:45 UTC

  • Feb 21, 2017
    • 15:47 UTC Some alert updates are delayed in Alert Web and Mobile UI. Notification flows are not effected.

      ACTIVITY

      • Resolved - Issue has been fully resolved Feb 21, 2017, 16:15 UTC

      • Updated - Fix has been rolled out to production, processes for recovering old delays has been started. Feb 21, 2017, 15:55 UTC

      • Updated - We identified the issue and trying to fix it. Feb 21, 2017, 15:48 UTC

  • Feb 12, 2017
    • 05:40 UTC Delays in creating alerts from incoming emails & integrations, API integrations & notifications service working as expected

      ACTIVITY

      • Updated - The root cause was a spike in traffic combined with excessive configuration in alert processing. Resolution: We identified potentially problematic configurations of existing customers and let them to fine tune them. Improvements: We modified processing power dynamics permanently to better handle such cases. We are already working on rate-limiting incoming data per customer, which will be released soon. We will be fine tuning hardcoded limits of customer-based configurations, so that this shall not happen again. Feb 12, 2017, 14:00 UTC

      • Resolved - Delays in all integrations has been resolved, some integration events processed with a max delay of 120 minutes. Processing power is at 6x than normal. During delays Alert API & notification services were working as normal, alerts created from email, Nagios, CloudWatch etc has been delayed. Root cause not identified yet, we will keep investigation going on and will keep processing power as much as needed. Feb 12, 2017, 10:40 UTC

      • Updated - Delays in processing incoming emails has resolved, some emails had delays maximum of 80 minutes. Processing power is 3x than normal. Delays in other integration event processing not fully resolved. Feb 12, 2017, 08:40 UTC

      • Updated - Initial investigation done, root cause not identified yet, some of integration events being delayed around 10 minutes. We started to add more processing power. Feb 12, 2017, 06:00 UTC

  • Dec 06, 2016
    • 14:55 UTC SMS, Voice, Email notifications started to be delayed after latest hotfix

      ACTIVITY

      • Resolved - Problem fixed and notification sending get back to normal Dec 06, 2016, 15:10 UTC

  • Nov 24, 2016
    • 16:30 UTC Team Details Page not working, alerting & notifications functional

      ACTIVITY

      • Resolved - Issue resolved. A bug in the UI code for the Team details page in the latest release determined as the cause. The release has been rolled back. Nov 24, 2016, 19:00 UTC

  • Nov 24, 2016
    • 13:00 UTC API Throttling activated, requests exceeding thresholds blocked

      ACTIVITY

      • Resolved - Issue resolved. A problem in the api key based throttling mechanism has caused api requests from some customers to get throttled. Logic has been rolled back. Nov 24, 2016, 19:45 UTC

  • Sep 14, 2016
    • 08:11 UTC Possible DNS resolution issues in some locations

      ACTIVITY

      • Resolved - The issue has been resolved Sep 14, 2016, 11:44 UTC

      • Updated - Problem affects customers in Sweden, Denmark and Spain Sep 14, 2016, 08:15 UTC

      • Updated - We are currently working to mitigate these issues Sep 14, 2016, 08:12 UTC

  • May 25, 2016
    • 00:30 UTC Erroneous repeating schedule notifications

      ACTIVITY

      • Updated - Schedule notification engine performance is improved as a persistent solution also. May 25, 2016, 09:30 UTC

      • Resolved - Schedule notification engine is back to normal, no more repeating occurs May 25, 2016, 01:15 UTC

      • Created - For some users schedule start & end notification trigger process was running very slow, even exceeding zombie process threshold which resulted in replay of the processes. As a result some users received start & end notifications multiple times. New computing resources already added we expect the problem to be resolved soon. May 25, 2016, 00:30 UTC

  • May 13, 2016
    • 12:38 UTC Log Service Is Down

      ACTIVITY

      • Resolved - Log service is up again. May 13, 2016, 14:11 UTC

      • Created - Logs page not showing log data temporarily. No log data will be lost during this interval. All other features, alerts & notifications working as expected. May 13, 2016, 12:41 UTC

  • Apr 06, 2016
    • 08:16 UTC Short API Outage for 3 minutes, caused by deployment automation, auto resolved

      ACTIVITY

      • Resolved - Outage automatically resolved as deployment process continued Apr 06, 2016, 08:19 UTC

      • Created - A bug in deployment logic, has started API Outage Apr 06, 2016, 08:16 UTC

  • Feb 17, 2016
    • 16:21 UTC Execution of alert custom actions does not work

      ACTIVITY

      • Resolved - The issue has been resolved Feb 17, 2016, 16:25 UTC

      • Created - After recent improvements we introduced a bug which prevents sending custom alert actions to external systems. Bug has been introduced at 09:00 AM UTC. Feb 17, 2016, 16:24 UTC

  • Dec 11, 2015
    • 15:00 UTC Reporting Service Is Down

      ACTIVITY

      • Resolved - The bug was introduced in the latest hotfix. Issue is resolved Feb 27, 2017, 16:45 UTC

      • Updated - All pending metrics are processed, reporting service back to normal. Dec 11, 2015, 21:20 UTC

      • Resolved - Reporting service is up, root cause was a capacity problem resulting to an outage. Reporting database version and capacity increased, no data is lost during process, pending metrics are being processed currently. Dec 11, 2015, 20:45 UTC

      • Created - Reporting page not showing metric data. All other features, alerts & notifications working as expected. Reporting service team is working on recovering the service. Dec 11, 2015, 15:00 UTC

  • Dec 04, 2015
    • 14:30 UTC Delays in SMS and Voice notifications

      ACTIVITY

      • Resolved - The problem is resolved with the latest hotfix, all delayed notifications are sent. Dec 04, 2015, 15:15 UTC

      • Created - A problem was introduced in the latest hotfix which prevents SMS and Voice notifications Dec 04, 2015, 14:30 UTC

  • Aug 04, 2015
    • 15:10 UTC Android application alerts page is getting parse errors

      ACTIVITY

      • Resolved - The issue has been resolved Aug 04, 2015, 15:55 UTC

      • Created - Latest hotfix has broken the api. We are working to fix the issue Aug 04, 2015, 15:12 UTC

  • May 29, 2015
    • 10:10 UTC OpsGenie Java SDK started getting "peer not authenticated" errors when accessing API

      ACTIVITY

      • Resolved - Updated https load balancer cipher settings to the latest valid settings and problem is resolved May 29, 2015, 15:15 UTC

      • Updated - Found out that the problem only impacts Java SDK running on Java 6, (Java 7 working fine), api is accessible by other languages & curl in the meantime, started investigation on the settings of the https load balancers May 29, 2015, 10:20 UTC

      • Created - Started investigation, the problem was reported by one of our external monitoring tools using OpsGenie Java SDK running on Java 6 May 29, 2015, 10:10 UTC

  • Apr 23, 2015
    • 18:00 UTC API Outage

      ACTIVITY

      • Resolved - API Fully recovered, details will be provided later on, Heartbeat, Alert & Integration APIs affected. Apr 23, 2015, 18:15 UTC

      • Updated - Started recovery of API Apr 23, 2015, 18:10 UTC

      • Updated - Full API Outage started Apr 23, 2015, 18:05 UTC

      • Created - Increased API Errors rates, started to investigate the reason Apr 23, 2015, 18:00 UTC

  • Oct 15, 2014
    • 06:02 UTC SSL fix for POODLE caused a problem in communications, impacting phone notifications.

      ACTIVITY

      • Resolved - fix reverted, phone notifications work again. Oct 15, 2014, 06:03 UTC

      • Updated - reverted the fix. Oct 15, 2014, 06:02 UTC

  • Jul 07, 2014
    • 15:05 UTC Heartbeat monitoring exceptions

      ACTIVITY

      • Resolved - Looks good. Jul 07, 2014, 16:29 UTC

      • Updated - Applied the hotfix and seems to have resolved the issue. We're monitoring the situation and checking the logs to verify that all is well Jul 07, 2014, 15:33 UTC

      • Updated - We apologize for the erroneous heartbeat expired alerts! Instead of rolling back, we've decided to apply a hotfix to resolve the problem. Jul 07, 2014, 15:19 UTC

      • Created - Heartbeat API requests return exception due to a bug in the deployed code. Rolling back the update. Jul 07, 2014, 15:05 UTC

  • Jun 24, 2014
    • 19:06 UTC Intermittent problems impacting Alert API

      ACTIVITY

      • Resolved - Issues detected between 17:26 and 18:10 UTC. We're investigating whether it had any impact on alert notifications. We will contact impacted customers. Jun 24, 2014, 19:13 UTC

      • Created - We've experience intermittent problems accessing underlying AWS services including the data store due to what seems to be authentication issues. Jun 24, 2014, 19:06 UTC

  • Jun 17, 2014
    • 21:20 UTC Phone notifications are failing due to a problem with the provider.

      ACTIVITY

      • Updated - We'll continue to work this closely but everything looks fine so far. Jun 18, 2014, 01:55 UTC

      • Resolved - Phone notifications are working via the secondary provider. Limited number of users may have been impacted prior to the switch. Analyzing logs and contacting the impacted users. Jun 18, 2014, 00:35 UTC

      • Created - We've started getting API exceptions when making calls, switching calls to a different provider. Jun 17, 2014, 21:20 UTC

  • Jun 03, 2014
    • 21:50 UTC Deployment of a hotfix broke OpsGenie web server authentication.

      ACTIVITY

      • Resolved - Hot fix is rolled back. Users are able to log back into the system Jun 03, 2014, 21:54 UTC

      • Created - Users were logged out, and cannot log back in. The problem prevents users from accessing the UI. No impact on alert transactions. Jun 03, 2014, 21:50 UTC

  • Feb 28, 2014
    • 08:35 UTC Alert create notifications not sent for customers using renotify policies after 9:00 AM GMT yesterday

      ACTIVITY

      • Resolved - The issue has been resolved. Feb 28, 2014, 10:00 UTC

      • Updated - We found the bug causing the problem. Will be fixed ASAP... Feb 28, 2014, 08:36 UTC