Live / Uniweb / Incident
Uniweb: Problemer med redirect-proxy – nedetid kan forekomme
Uniweb · uniweb.noMajor incidentResolved2026-11-02 17:54 UTC
Public — what happened
Summary
Uniweb said its redirect proxy service was having problems starting 31 October 2026 at 19:22 UTC, which could make the service intermittently unavailable. The company said customers might find that DNS 301 forwarding for their domains had stopped working. Uniweb said its engineers were working on it, and at 21:31 UTC it reported that a fix had been put in place and it was monitoring the results. The incident was marked resolved on 2 November 2026 at 17:54, and no cause was given in the text.
Affected
Web Forwarding
Timeline
- Started — 2026-10-31 19:22 UTC
- Investigating — 2026-10-31 19:22 UTC
- Monitoring — 2026-10-31 21:31 UTC
- Resolved — 2026-11-02 17:54 UTC · 46h 32m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Uniweb against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Uniweb: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Uniweb report →
More from Uniweb
Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.