Live  /  Providers  /  Feeder

Feeder

feeder.coNo open incidents

Independent assessment — SquidGrid is not affiliated with Feeder. 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 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

Resolved

API is down (resolved)

2026-11-10 12:46 UTC · source

Resolved

Website & app is down (resolved)

2026-11-10 12:46 UTC · source

Resolved

API is down (resolved)

2026-11-10 06:07 UTC · source

Resolved

Website & app is down (resolved)

2026-11-10 06:07 UTC · source

Resolved

API is down (resolved)

2026-10-28 16:49 UTC · source

Resolved

Website & app is down (resolved)

2026-10-28 16:49 UTC · source

Resolved

Website & app is down (investigating)

2026-10-28 16:27 UTC · source

Resolved

API is down (investigating)

2026-10-28 16:27 UTC · source

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

Track record

SquidGrid has archived 29 incidents from Feeder’s own status page since 2026-08-18.

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

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.

SquidGrid is not affiliated with Feeder.