eBoundHost Outage History

eBoundHost is up right now

Pingoru has recorded 16 incidents for eBoundHost: 1 in the last 12 months and 0 in the last 90 days.

Source: eboundhost-status.com

16incidents recorded
1last 12 months
0last 90 days
27 hourstypical duration

Incidents, newest first

Critical June 13, 2026 Upstream Network Disruption – Service Degradation 1d 2h eBoundHost Network, JetRails Managed Network

Started Jun 13, 2026, 10:49 PM UTC· resolved Jun 15, 2026, 01:20 AM UTC

  1. investigating Jun 13, 2026, 10:49 PM UTC

    We are currently investigating reports of service disruption affecting Chicago Data Center facility. Our upstream network provider is experiencing a DDoS attack which is impacting connectivity. Our team is actively monitoring the situation and coordinating with the provider for resolution. We will post further updates as more information becomes available.

  2. investigating Jun 14, 2026, 03:11 AM UTC

    The incident has been identified as a volumetric DDoS attack affecting network connectivity. Our team is actively working with our upstream network providers to restore normal operation. We will continue to provide updates as the situation progresses.

  3. identified Jun 14, 2026, 05:07 AM UTC

    Mitigation efforts for the ongoing DDoS attack are still in progress. Our team continues to work with our network providers to restore normal service. The next update will follow soon.

  4. monitoring Jun 14, 2026, 10:21 PM UTC

    At this time we are pleased to report that our team has successfully remediated the volumetric DDoS attack affecting network connectivity. Service has been restored and we are continuing to monitor the situation closely. We will post a final update to confirm sustained stability.

  5. resolved Jun 15, 2026, 01:20 AM UTC

    Our team has successfully mitigated the volumetric DDoS attack that affected network connectivity. Service has been fully restored and our network is operating normally. We have implemented additional protective measures to further safeguard against future disruptions. We sincerely apologize for the inconvenience this has caused and thank you for your patience throughout this incident. We will be publishing a full post-incident report shortly.

Read the full incident report →