Live / Providers / Feeder
Feeder
feeder.coNo open incidents
SaaS & business software · SquidGrid tracks Feeder’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 Feeder is reporting
Current & recent incidents
ResolvedAPI is down (resolved)
2026-11-10 12:46 UTC · source
ResolvedWebsite & app is down (resolved)
2026-11-10 12:46 UTC · source
ResolvedAPI is down (resolved)
2026-11-10 06:07 UTC · source
ResolvedWebsite & app is down (resolved)
2026-11-10 06:07 UTC · source
ResolvedAPI is down (resolved)
2026-10-28 16:49 UTC · source
ResolvedWebsite & app is down (resolved)
2026-10-28 16:49 UTC · source
ResolvedWebsite & app is down (investigating)
2026-10-28 16:27 UTC · source
ResolvedAPI is down (investigating)
2026-10-28 16:27 UTC · source
Track record
SquidGrid has archived 29 incidents from Feeder’s own status page since 2026-08-18.
- Most recent incident: 5 days ago
- Status page last checked 2026-11-16 01:08 UTC
With SquidGrid — where the route changes
Independent path health
A status page tells you what Feeder 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.
Feeder 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 Feeder is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.
🔒 Sign in to see
Incident track record: 90-day trend, median and worst time to fix
What tends to break, from their own incident write-ups
Recent public reports of problems with this service
Included with any paid plan.
See the full report →