All Systems Operational

About This Site

Welcome to Hull's home for real-time information about our system status. Here you'll find current and historical data on system performance. If there are any interruptions in service, a note will be posted here.

Hull Core Platform Operational
90 days ago
100.0 % uptime
Today
Hull API ? Operational
90 days ago
100.0 % uptime
Today
hull.js CDN ? Operational
Hull Background Worker Operational
Hull Authentication Subsystem Operational
90 days ago
100.0 % uptime
Today
Hull Social Login ? Operational
90 days ago
100.0 % uptime
Today
Hull App Login ? Operational
Hull Cloud Infrastructure Operational
Heroku Operational
AWS route53 Operational
Google Cloud Platform Google Cloud Pub/Sub Operational
Google Cloud Platform Google Cloud Storage Operational
Hull Connectors ? Operational
Clearbit Connector ? Operational
Datanyze Connector ? Operational
Facebook Audiences Connector Operational
Hubspot Connector ? Operational
Intercom Connector Operational
Mailchimp Connector Operational
Nutshell Connector Operational
Processor ? Operational
Salesforce Connector ? Operational
Segment Connector Operational
Slack Connector Operational
SQL Connector Operational
Typeform Connector Operational
Intercom Operational
Intercom Intercom APIs Operational
Intercom Intercom Webhooks Operational
Salesforce Asia ? Operational
Salesforce AP0 Operational
Salesforce AP2 Operational
Salesforce AP3 Operational
Salesforce AP4 Operational
Salesforce CS31 Operational
Salesforce AP1 Operational
Salesforce Americas ? Operational
Salesforce CS1 Operational
Salesforce CS3 Operational
Salesforce CS2 Operational
Salesforce CS10 Operational
Salesforce CS11 Operational
Salesforce CS12 Operational
Salesforce CS13 Operational
Salesforce CS14 Operational
Salesforce CS15 Operational
Salesforce CS16 Operational
Salesforce CS17 Operational
Salesforce CS18 Operational
Salesforce CS19 Operational
Salesforce CS20 Operational
Salesforce CS21 Operational
Salesforce CS22 Operational
Salesforce CS23 Operational
Salesforce CS24 Operational
Salesforce CS26 Operational
Salesforce CS28 Operational
Salesforce CS27 Operational
Salesforce CS30 Operational
Salesforce CS25 Operational
Salesforce CS32 Operational
Salesforce CS33 Operational
Salesforce CS40 Operational
Salesforce CS41 Operational
Salesforce CS42 Operational
Salesforce CS43 Operational
Salesforce CS44 Operational
Salesforce CS45 Operational
Salesforce CS4 Operational
Segment Operational
Segment Integrations Operational
Segment Analytics.js CDN Operational
Segment Cloud Sources Operational
Segment Tracking API Operational
Slack Operational
Slack Operational
Stripe Operational
Stripe API Operational
Stripe Webhooks Operational
Stripe Checkout.js Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
System Metrics Month Week Day
DNS Health Percentage ?
Fetching
Past Incidents
Aug 19, 2017

No incidents reported today.

Aug 18, 2017

No incidents reported.

Aug 17, 2017

No incidents reported.

Aug 16, 2017

No incidents reported.

Aug 15, 2017
Resolved - After extended monitoring, we can confirm that all nodes are fully operational. We apologize for any delay in processing and will analyze options to mitigate this kind of incidents in the future.
Aug 15, 16:38 EDT
Monitoring - Our DevOps team has taken manual steps to move service nodes from the failing infrastructure and the Clearbit Connector is fully operational again.
Next Steps: We continue close monitoring of the service to ensure the service health. The next update will be published as events warrant or when the Incident Commander declares this incident as resolved.
Aug 15, 12:52 EDT
Identified - Our DevOps team has been notified of another failure in the underlying infrastructure and has taken manual action to mitigate the impact. The failed requests will be retried automatically - no data is loss.
Next Steps: We continue close monitoring of the service to ensure the service health. The next update will be published as events warrant or within 60 minutes.
Aug 15, 11:31 EDT
Monitoring - Our DevOps team has taken manual steps to move service nodes from the failing infrastructure and the Clearbit Connector is fully operational again.
Next Steps: We continue close monitoring of the service to ensure the service health. The next update will be published as events warrant or when the Incident Commander declares this incident as resolved.
Aug 15, 10:25 EDT
Identified - We have identified the root cause of the outage which was a failing infrastructure component.
Next Steps: Our DevOps Team is moving service nodes away from the affected infrastructure to restore operational status of the Connector. The next update will be published as events warrant or within the next 60 minutes.
Aug 15, 10:06 EDT
Investigating - The Clearbit Connector is currently suffering from an outage. We are actively investigating the root cause and will post another update as events warrant or within the next 30 minutes.
Aug 15, 09:39 EDT
Aug 14, 2017

No incidents reported.

Aug 13, 2017

No incidents reported.

Aug 12, 2017

No incidents reported.

Aug 11, 2017

No incidents reported.

Aug 10, 2017
Postmortem - Read details
Aug 11, 11:46 EDT
Resolved - Incident declared as resolved after extended monitoring period. The load stays consistent and traffic spikes have been handled appropriately within the last couple of hours.
Next Steps: A post-mortem report will be published within the next business days.
Aug 10, 23:46 EDT
Monitoring - Our Ops team confirmed the effectiveness of the hotfix and is monitoring the Connector closely to ensure operational status. Performance returned to normal at approximately at 16:50 UTC on 08/10/2017.
Next steps: Another update will be published as soon as the issue is fully resolved.
Aug 10, 20:24 EDT
Identified - Our DevOps Team has identified the root cause which was a failure in the queue system. This caused an increase in the backlog of the queue due to multiple retries and resulted in performance degradations. Our DevOps teams have issued a hotfix at 13:35 UTC on 08/10/2017.
Next Steps: We are monitoring the effectiveness of the hotfix. Another update will be published as soon as events warrant.
Aug 10, 20:21 EDT
Investigating - Beginning at approximately 02:15 UTC on 08/09/2017 customers might experience delays in processing of Intercom data due to a huge traffic spike on the Connector. Scaling the service to multiple instances didn't mitigate the problem. Our DevOps team is working to identify the root cause.
Aug 10, 09:22 EDT
Resolved - All data is processed without further delays. Ops has confirmed that the incident was caused by intermittent unavailability of service endpoints from our cloud provider. We apologize for any inconveniences this may have caused.
Aug 10, 20:47 EDT
Identified - DevOps has identified the root cause of the performance degradation which are problems in the underlying infrastructure of our cloud service provider. This causes requests to fail and being retried. We can confirm that all data is handled properly but with a delay of several minutes.
Next Steps: We will monitor the situation closely and publish another updated as events warrant.
Aug 10, 20:29 EDT
Investigating - Beginning at approximately 23:32 UTC on 08/10/2017 customers might experience some delays when executing custom scripts with the Processor. Another status update will be issued within the next 30 minutes or as events warrant.
Aug 10, 20:15 EDT
Aug 9, 2017

No incidents reported.

Aug 8, 2017

No incidents reported.

Aug 7, 2017

No incidents reported.

Aug 6, 2017

No incidents reported.

Aug 5, 2017

No incidents reported.