- Detected by Pingoru
- Sep 06, 2026, 07:00 AM UTC
- Resolved
- Sep 06, 2026, 08:00 AM UTC
- Duration
- 1h
Affected: 🐙 Octotel Fibre
Timeline · 2 updates
-
investigating Sep 06, 2026, 07:00 AM UTC
Please note that Octotel is currently experiencing a network outage which is affecting some customers in CBD precincts. Their engineers are currently investigating. More updates to follow.
-
resolved Sep 06, 2026, 08:00 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 04, 2026, 11:30 AM UTC
- Resolved
- Sep 11, 2026, 08:27 AM UTC
- Duration
- 6d 20h
Affected: 🐰 Vumatel Fibre
Timeline · 3 updates
-
investigating Sep 04, 2026, 11:30 AM UTC
We are aware of an outage on the Vumatel network. Vumatel is busy investigating.
-
identified Sep 09, 2026, 08:00 AM UTC
Vumatel has restarted repairs on the fibre line. Delays were caused by Vumatel needing to source more hardware for the repair.
-
identified Sep 09, 2026, 01:19 PM UTC
Vumatel has started splicing the fibre cables but we still do not have a current ETR for the fibre outage.
Read the full incident report →
- Detected by Pingoru
- Aug 31, 2026, 04:00 PM UTC
- Resolved
- Aug 31, 2026, 05:00 PM UTC
- Duration
- 1h
Affected: ⚛️ Atomic Systems (📬 Email & Ticket System)
Timeline · 3 updates
-
identified Aug 31, 2026, 12:39 PM UTC
Please note that we're currently experiencing a system outage which is impacting our ticketing and email platforms. Kindly be advised that our response times will unfortunately be delayed until the problem is resolved. We sincerely apologize for the the inconvenience.
-
monitoring Aug 31, 2026, 04:00 PM UTC
We implemented a fix and are currently monitoring the result.
-
resolved Aug 31, 2026, 05:00 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 03, 2026, 12:27 PM UTC
- Resolved
- Aug 03, 2026, 03:27 PM UTC
- Duration
- 2h 59m
Affected: 🐙 Octotel Fibre
Timeline · 2 updates
-
investigating Aug 03, 2026, 12:27 PM UTC
Please note that Octotel have identified an issue on their network affecting services around the Strand area. Octotel technicians are currently investigating. More updates to follow.
-
resolved Aug 03, 2026, 03:27 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 31, 2026, 01:08 PM UTC
- Resolved
- Aug 01, 2026, 08:08 AM UTC
- Duration
- 18h 59m
Affected: 🚠 Upstream Networks (🌎 IP Transit 2)
Timeline · 2 updates
-
investigating Jul 31, 2026, 01:08 PM UTC
We are currently experiencing degraded performance on this upstream. We are working with our provider in order to resolve this issue.
-
resolved Aug 01, 2026, 08:08 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 24, 2026, 08:56 AM UTC
- Resolved
- Jul 24, 2026, 03:00 PM UTC
- Duration
- 6h 3m
Affected: 🦎 Openserve Fibre
Timeline · 2 updates
-
investigating Jul 24, 2026, 08:56 AM UTC
We are aware of an outage on the Openserve network. Openserve is busy investigating.
-
resolved Jul 24, 2026, 03:00 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 20, 2026, 01:31 PM UTC
- Resolved
- Aug 19, 2026, 01:49 PM UTC
- Duration
- 30d
Affected: 🚠 Upstream Networks (🌍 IP Transit 1)
Timeline · 1 update
-
monitoring Jul 20, 2026, 01:31 PM UTC
We are aware of the issues causing disruption during peak times. Our upstream provider is currently working on increasing capacity but we currently do not have an ETR. We apologies for the inconvenience this has caused.
Read the full incident report →
- Detected by Pingoru
- Jul 20, 2026, 11:00 AM UTC
- Resolved
- Jul 31, 2026, 05:13 PM UTC
- Duration
- 11d 6h
Affected: 🚠 Upstream Networks (👽 NAP JHB 2)
Timeline · 1 update
-
identified Jul 20, 2026, 11:00 AM UTC
We are aware of the outage affecting one of our Joburg upstream. Our provider is currently aware of the issue and are working to resolve it.
Read the full incident report →
- Detected by Pingoru
- Jun 08, 2026, 07:24 AM UTC
- Resolved
- Jun 08, 2026, 07:00 PM UTC
- Duration
- 11h 35m
Affected: 🐙 Octotel Fibre
Timeline · 2 updates
-
identified Jun 08, 2026, 07:24 AM UTC
We are aware of an outage on the Octotel network. Octotel is busy investigating.
-
resolved Jun 08, 2026, 07:00 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 28, 2026, 07:00 AM UTC
- Resolved
- May 28, 2026, 12:20 PM UTC
- Duration
- 5h 19m
Affected: 🐙 Octotel Fibre
Timeline · 2 updates
-
investigating May 28, 2026, 07:00 AM UTC
We are aware of an outage on the Octotel network. Octotel is busy investigating.
-
resolved May 28, 2026, 12:20 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 27, 2026, 09:07 AM UTC
- Resolved
- May 27, 2026, 11:33 AM UTC
- Duration
- 2h 26m
Affected: 🚠 Upstream Networks (🌎 IP Transit 2)
Timeline · 3 updates
-
identified May 27, 2026, 09:07 AM UTC
We have noticed elevated latency to certain destinations.
-
monitoring May 27, 2026, 09:33 AM UTC
We implemented a fix and are currently monitoring the result.
-
resolved May 27, 2026, 11:33 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 22, 2026, 06:18 AM UTC
- Resolved
- May 22, 2026, 10:04 AM UTC
- Duration
- 3h 46m
Affected: 🦎 Openserve Fibre
Timeline · 2 updates
-
investigating May 22, 2026, 06:18 AM UTC
Please note that we are aware of an outage on Openserve's network in Welgemoed and surrounding areas. We're following up with our Openserve Management team this morning for more information.
-
resolved May 22, 2026, 10:04 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 19, 2026, 12:30 PM UTC
- Resolved
- May 20, 2026, 12:00 PM UTC
- Duration
- 23h 30m
Affected: 🚠 Upstream Networks (🌎 IP Transit 2)
Timeline · 3 updates
-
identified May 19, 2026, 12:30 PM UTC
We are aware of an increase International latency on the Atomic network. We are busy investigating.
-
identified May 19, 2026, 02:00 PM UTC
We are aware of an increase International latency on the Atomic network. We are busy investigating.
-
resolved May 20, 2026, 12:00 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 16, 2026, 11:41 AM UTC
- Resolved
- May 17, 2026, 07:35 AM UTC
- Duration
- 19h 54m
Affected: 🐸 Frogfoot Fibre
Timeline · 2 updates
-
investigating May 16, 2026, 11:41 AM UTC
We are aware of an outage on the Frogfoot network. Frogfoot is busy investigating.
-
resolved May 17, 2026, 07:35 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 13, 2026, 02:30 PM UTC
- Resolved
- May 21, 2026, 09:09 AM UTC
- Duration
- 7d 18h
Affected: 🚠 Upstream Networks (🌍 IP Transit 1)
Timeline · 2 updates
-
investigating May 13, 2026, 02:30 PM UTC
We have are currently seeing higher latency and packet loss on our primary upstream and have decided to shut it down until resolved. All international traffic will now be routed through our secondary upstream.
-
monitoring May 13, 2026, 02:31 PM UTC
We have are currently seeing higher latency and packet loss on our primary upstream and have decided to shut it down until resolved. All international traffic will now be routed through our secondary upstream.
Read the full incident report →
- Detected by Pingoru
- May 08, 2026, 01:25 PM UTC
- Resolved
- May 08, 2026, 05:45 PM UTC
- Duration
- 4h 19m
Affected: 🐙 Octotel Fibre
Timeline · 2 updates
-
investigating May 08, 2026, 01:25 PM UTC
Please note that we are aware of an outage on Octotel's fibre network. Customers in the Milnerton and Parklands areas connected to the Blouberg node may experience disruptions in service. Octotel technicians are currently investigating. More updates to follow.
-
resolved May 08, 2026, 05:45 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 05, 2026, 02:39 PM UTC
- Resolved
- May 05, 2026, 04:45 PM UTC
- Duration
- 2h 5m
Affected: 🐸 Frogfoot Fibre
Timeline · 2 updates
-
identified May 05, 2026, 02:39 PM UTC
We are aware of an outage on the Frogfoot network. Frogfoot is busy investigating.
-
resolved May 05, 2026, 04:45 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 05, 2026, 07:48 AM UTC
- Resolved
- May 05, 2026, 08:00 AM UTC
- Duration
- 11m
Affected: 🚠 Upstream Networks (🌍 IP Transit 1)🚠 Upstream Networks (🌎 IP Transit 2)
Timeline · 3 updates
-
investigating May 05, 2026, 07:48 AM UTC
We are aware of an outage on the Atomic network. We are busy investigating.
-
monitoring May 05, 2026, 07:57 AM UTC
We implemented a fix and are currently monitoring the result.
-
resolved May 05, 2026, 08:00 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 30, 2026, 01:15 PM UTC
- Resolved
- Apr 30, 2026, 02:20 PM UTC
- Duration
- 1h 5m
Affected: 🚠 Upstream Networks (👽 NAP JHB 2)
Timeline · 3 updates
-
investigating Apr 30, 2026, 01:15 PM UTC
We are aware of an outage on the upstream network and our upstream provider is working to resolve the issue.
-
identified Apr 30, 2026, 01:45 PM UTC
We are aware of an outage on the upstream network and our upstream provider is working to resolve the issue.
-
resolved Apr 30, 2026, 02:20 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 30, 2026, 09:59 AM UTC
- Resolved
- May 01, 2026, 09:25 AM UTC
- Duration
- 23h 26m
Affected: 🐙 Octotel Fibre
Timeline · 2 updates
-
investigating Apr 30, 2026, 09:59 AM UTC
Please note that we are aware of an outage on Octotel's network which is affecting services around Ruyterwacht, Andriaanse and the Clarkes areas . Octotel's technicians are currently investigating.
-
resolved May 01, 2026, 09:25 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 30, 2026, 09:57 AM UTC
- Resolved
- May 02, 2026, 07:39 AM UTC
- Duration
- 1d 21h
Affected: 🐸 Frogfoot Fibre
Timeline · 2 updates
-
investigating Apr 30, 2026, 09:57 AM UTC
Please note that we are aware of an outage on Frogfoot's network which is affecting services around Gordon's Bay. Frogfoot technicians are currently investigating.
-
resolved May 02, 2026, 07:39 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 20, 2026, 07:47 AM UTC
- Resolved
- Apr 20, 2026, 07:47 AM UTC
- Duration
- —
Affected: Overall
Read the full incident report →
- Detected by Pingoru
- Apr 16, 2026, 05:00 PM UTC
- Resolved
- Apr 16, 2026, 05:00 PM UTC
- Duration
- —
Affected: Overall
Read the full incident report →
- Detected by Pingoru
- Apr 12, 2026, 06:30 PM UTC
- Resolved
- Apr 12, 2026, 06:30 PM UTC
- Duration
- —
Affected: Overall
Read the full incident report →
- Detected by Pingoru
- Apr 10, 2026, 02:40 PM UTC
- Resolved
- Apr 10, 2026, 02:40 PM UTC
- Duration
- —
Affected: Overall
Read the full incident report →