EBSCO Status

Official pageUpdated
GOBI Service Issue - Investigating
investigating · Started · Advisory
View incident →
BiblioGraph
DynaMed Decisions
DynaMed
DynaMedex
Dynamic Health
EBSCOadmin
EBSCO Connect
EBSCOhost Research Databases
EBSCO Discovery Service
EBSCO Discovery Service API
EBSCO eBooks
EBSCOhost Collection Manager
EBSCO Experience Manager
EBSCO Mobile App
EBSCONET
Explora
Flipster
FOLIO
Full Text Finder Resolver
GOBI
Holdings and Link Management
LibraryAware
Mosaic
NoveList
Publication Finder
1–25 of 27 components

Incident overview

Total incidents

10

Active now

1

Resolved

9

Avg. resolution

12h 12m

Frequently asked questions

Is EBSCO down right now?

EBSCO is currently experiencing issues with 1 active incident. Current status: Operational. Check the incident details above for more information.

What is EBSCO's current uptime?

Uptime data for EBSCO is still being collected. DevHelm needs sufficient monitoring data before reporting uptime percentages. Check back soon.

How many incidents has EBSCO had recently?

EBSCO has experienced 10 incidents in the recent monitoring window. Resolved incidents were fixed in an average of 12h 12m. 1 incident is currently active.

What components does EBSCO monitor?

DevHelm tracks 27 individual components for EBSCO, including BiblioGraph, DynaMed Decisions, DynaMed, DynaMedex, Dynamic Health, and 22 more. Each component has its own status and 90-day uptime history shown above.

How can I get notified about EBSCO outages?

You can subscribe to EBSCO's incident feed via Atom/RSS at devhelm.io/status/ebsco/feed.xml for use in any feed reader. For real-time alerts via Slack, email, PagerDuty, or webhooks, add EBSCO as a dependency in your DevHelm workspace.

About EBSCO status monitoring

This page provides real-time operational status for EBSCO, powered by DevHelm's continuous monitoring infrastructure. We track EBSCO's official status page and aggregate component-level data into uptime percentages, incident timelines, and historical trends.

EBSCO status data is refreshed every 30 seconds. We currently track 27 individual components, each with its own operational status and 90-day uptime history.

Uptime percentages represent the proportion of time all monitored components reported operational status. Incident data comes from vendor-published incident timelines and includes status updates, affected components, and resolution times.

Track EBSCO in your stack

Get alerted when EBSCO has issues — before your users notice. Set up in 30 seconds.

Start Free →