Live  /  Providers  /  Webland

Webland

webland.chReporting incidents

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

Current & recent incidents

investigating

Wartungsarbeiten Windows Updates

None impact · 2026-11-12 10:49 UTC · source

investigating

Kritische PHP-Sicherheitslücke (PHP2Shell) – Schutzmassnahmen eingeleitet

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

Resolved

Erhöhte Serverlast auf einzelnen Mailservern

Minor impact · 2026-10-26 11:07 UTC · source

Resolved

Kritische WordPress-Sicherheitslücke (WP2Shell)

None impact · 2026-10-14 08:32 UTC · source

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

Track record

SquidGrid has archived 14 incidents from Webland’s own status page since 2026-07-20: 11 in the last 90 days.

Recent incidents in the archive

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

Independent path health

A status page tells you what Webland 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.

Webland 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 Webland is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.

SquidGrid is not affiliated with Webland.