Live  /  Providers  /  EBSCO

EBSCO

ebsco.comReporting incidents

Independent assessment — SquidGrid is not affiliated with EBSCO. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

SaaS & business software · SquidGrid tracks EBSCO’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.

Public — what EBSCO is reporting

Current & recent incidents

monitoring

GOBI Service Issue - Monitoring

None impact · 2026-11-13 14:51 UTC · still open per the provider’s page — may be stale · source

Resolved

Service Issue Reported – Stacks Access Issues

Major impact · 2026-10-22 14:41 UTC · source

Resolved

Service Issue Reported – EBSCONET

Critical impact · 2026-10-16 02:29 UTC · source

Resolved

Service Issue Reported – Mosaic

Critical impact · 2026-10-06 18:06 UTC · source

Resolved

Service Issue Reported – STACKS

Minor impact · 2026-09-03 15:36 UTC · source

Incident titles and states as published by the provider. Times in UTC.

Track record

SquidGrid has archived 7 incidents from EBSCO’s own status page since 2026-09-01.

Recent incidents in the archive

Computed by SquidGrid from the incidents EBSCO published. Their own page shows only recent history; this archive keeps every one.

Independent path health

A status page tells you what EBSCO has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.

EBSCO runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of EBSCO is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.

SquidGrid is not affiliated with EBSCO.