EBSCO incident
Service Issue Reported – ***EBSCO Discovery Service, EBSCO eBooks, EBSCO Mobile App, EBSCOhost Research Databases, Explora, Flipster, Full Text Finder Resolver, Holdings and Link Management, OpenURL Connection, Publication Finder***
EBSCO experienced a major incident on June 24, 2026 affecting DynaMed Decisions and DynaMed and 1 more component, lasting 2h 18m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 24, 2026, 06:58 AM UTC
We have received reports of an issue with EBSCO Discovery Service, EBSCO eBooks, EBSCO Mobile App, EBSCOhost Research Databases, Explora, Flipster, Full Text Finder Resolver, Holdings and Link Management, OpenURL Connection, Publication Finder. Our engineering teams are currently investigating the issue and we will update this page when more information is available.
- investigating Jun 24, 2026, 07:12 AM UTC
We are continuing to investigate this issue.
- investigating Jun 24, 2026, 07:39 AM UTC
We are continuing to investigate this issue.
- investigating Jun 24, 2026, 07:39 AM UTC
We are continuing to investigate this issue.
- identified Jun 24, 2026, 08:56 AM UTC
Our engineering teams have identified the issue impacting our products and are currently working to resolve this issue. We will update this page when more information is available.
- monitoring Jun 24, 2026, 09:11 AM UTC
We appreciate your patience while we investigated the reported system issue. Currently we have resolved the following: *EBSCO Discovery Service, *EBSCO eBooks, *EBSCO Mobile App, *EBSCOhost Research Databases, *Explora, *Flipster, *Full Text Finder Resolver, *Holdings and Link Management, *OpenURL Connection, *Publication Finder, *EBSCO Discovery Service API, *DynaMed Decisions, *DynaMed, *DynaMedex, *Dynamic Health. If you do not see your issue updated, we are continuing to investigate and resolve the issues and will provide additional updates as information is available.
- resolved Jun 24, 2026, 09:17 AM UTC
The issues reported are now resolved. If you continue to experience an issue please contact Customer Support. We apologize for the inconvenience.