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
99.98 % uptime
Today
Hull API   ? Operational
90 days ago
99.98 % uptime
Today
hull.js CDN   ? Operational
Hull Background Worker   Operational
Logs   ? 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
Customer.io Connector   Operational
Outgoing Webhooks Connector   Operational
Incoming Webhooks Connector   Operational
Optimizely Connector   Operational
Close.io Connector   Operational
Scheduled Calls   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
DNS Health Percentage ?
Fetching
Dashboard logs delay
Fetching
Past Incidents
Apr 25, 2018

No incidents reported today.

Apr 24, 2018

No incidents reported.

Apr 23, 2018

No incidents reported.

Apr 22, 2018

No incidents reported.

Apr 21, 2018

No incidents reported.

Apr 20, 2018

No incidents reported.

Apr 19, 2018
Completed - Maintenance has been completed successfully.
Apr 19, 23:59 EDT
Verifying - We are verifying the migration results, maintenance is expected to be completed within the next 20 minutes.
Apr 19, 23:27 EDT
Update - Maintenance is progressing as planned, completion of all tasks will take about an hour longer than originally planned.
Apr 19, 22:21 EDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 19, 21:01 EDT
Scheduled - A recent update to the Hull Dashboard requires the migration of the account settings in all Salesforce Connectors. Engineers will perform an automated migration for each customer in the maintenance period. We expect a short downtime of a couple of seconds for each affected connector before the synchronization resumes. No data will be affected and there are no actions required from you as a customer.
Apr 19, 20:00 EDT
Resolved - Ingestion backlog is now consumed.
Apr 19, 11:03 EDT
Monitoring - Logs are significantly delayed across all organizations; this is only affecting the logs for connectors, there is no impact on the data, data is still processed regularly.
Apr 19, 08:02 EDT
Apr 18, 2018
Resolved - Summary of Impact:
Between 19:40 UTC on Apr 17 and 00:15 UTC on Apr 18 the synchronization of outgoing data has been interrupted by an outage of the underlying service. No data has been lost during this period and operations resumed at 00;15 UTC. Incoming data was not affected.

Root cause:
A CPU intensive operation caused the service to become unstable over time which resulted in messages not being transported from the platform to the connectors. The service was unable to recover itself which made manual intervention necessary.

Next steps:
A complete post-mortem will be published within the next 48 hours. We apologize for any inconveniences this may have caused our customers and hope to regain your trust by the steps taken.
Apr 18, 10:12 EDT
Monitoring - Summary of Impact:
Between 19:40 UTC on Apr 17 and 00:15 UTC on Apr 18 the synchronization of outgoing data has been interrupted by an outage of the underlying service. No data has been lost during this period and operations resumed at 00;15 UTC. Incoming data was not affected.

Root cause:
A CPU intensive operation caused the service to become unstable over time which resulted in messages not being transported from the platform to the connectors. The service was unable to recover itself which made manual intervention necessary.

Next steps:
Engineers have deployed a hotfix, restored operations and will continue monitoring the resolution. Another update will be issued as events warrant.
Apr 17, 20:23 EDT
Identified - Investigating - Summary of Impact:
Starting at 19:40 UTC the synchronization of outgoing data has been interrupted by an outage of the underlying service. Data will be processed once the issue has been resolved. Incoming data is not affected.

Preliminary root cause:
A CPU intensive operation caused the service to become unstable over time which resulted in messages not being transported from the platform to the connectors.

Next steps:
Engineers are working on a hotfix to restore operations. Another update will be issued within the next 90 minutes or as events warrant
Apr 17, 17:51 EDT
Investigating - Summary of Impact:
Starting at 19:40 UTC the synchronization of outgoing data has been interrupted by an outage of the underlying service. Data will be processed once the issue has been resolved. Incoming data is not affected.

Next steps:
Engineers are investigating the root cause of this issue. Another update will be issued within the next 30 minutes or as events warrant
Apr 17, 15:47 EDT
Apr 16, 2018

No incidents reported.

Apr 15, 2018
Resolved - This incident has been resolved.
Apr 15, 10:09 EDT
Identified - Summary of Impact:
Starting at 19:20 UTC logs are significantly delayed across all organizations; this is only affecting the logs for connectors, there is no impact on the data, data is still processed regularly.

Preliminary Root Cause:
Several large traffic spikes in logs increased the processing time significantly.

Next steps:
Engineers will monitor the situation and take preventive measurements to ensure that the latency is being reduced. Another updated will be issued as events warrant.
Apr 13, 15:49 EDT
Investigating - Summary of Impact:
Starting at 19:20 UTC logs are significantly delayed across all organizations; this is only affecting the logs for connectors, there is no impact on the data, data is still processed regularly.

Next steps:
Engineers are investigating the root cause of this issue.
Apr 13, 15:47 EDT
Apr 14, 2018

No incidents reported.

Apr 13, 2018
Resolved - This incident has been resolved.
Apr 13, 08:04 EDT
Monitoring - Backlog of jobs is being processed, the delay of processing is going down as well.
Apr 13, 07:28 EDT
Investigating - High traffic is causing logs to be delayed for several hours. Our engineering team is investigating the root cause of the issue. We will issue another update within 120 minutes or as events warrant.
Apr 13, 04:57 EDT
Apr 12, 2018
Resolved - Summary of impact:
Between approximately 19:06 UTC and 19:50 UTC on 12 Apr 2018, we experienced several intermittent network issues on parts of our service. Incoming data during this period might have been lost if it cannot be retried, such as for webhooks.

Root cause:
Intermittent network issues on Heroku which runs part of our service caused parts of the service not being available. The network issues were originating from a full logs directory in one of the database services.

Next steps:
Engineers have recovered the full logs directory manually and will deploy an automated failover solution in the next days to prevent this situation from happening again. We apologize for any inconveniences this may have caused.
Apr 12, 22:45 EDT
Monitoring - Summary of impact:
Between approximately 19:06 UTC and 19:50 UTC on 12 Apr 2018, we experienced several intermittent network issues on parts of our service. Incoming data during this period might have been lost if it cannot be retried, such as for webhooks.

Preliminary root cause:
Intermittent network issues on Heroku which runs part of our service caused parts of the service not being available. The network issues were originating from a full logs directory in one of the database services.

Next steps:
Engineers will continue monitoring the situation closely.
Apr 12, 15:01 EDT
Investigating - Summary of impact:
Engineers are currently investigating networking issues with the Heroku infrastructure which started at approximately 19:06 UTC.

Next steps:
Engineers are investigating the root cause. An update will be posted within the next 15 to 30 minutes or as events warrant.
Apr 12, 14:38 EDT
Apr 11, 2018

No incidents reported.