Fiberspark Outage History
Fiberspark is up right nowPingoru has recorded 4 incidents for Fiberspark: 4 in the last 12 months and 4 in the last 90 days.
Incidents, newest first
Major October 31, 2026 www.fiberspark.com is back up 2m Fiberspark Websites (Fiberspark Website (www.fiberspark.com))
Started Oct 31, 2026, 06:00 PM UTC· resolved Oct 31, 2026, 06:03 PM UTC
- investigating Oct 31, 2026, 06:00 PM UTC
Fiberspark Website (www.fiberspark.com) is down at the moment. This incident was automatically created by Instatus monitoring.
- resolved Oct 31, 2026, 06:03 PM UTC
Fiberspark Website (www.fiberspark.com) is back up. This incident was automatically resolved by Instatus monitoring.
Major October 26, 2026 www.fiberspark.com is back up 2m Fiberspark Websites (Fiberspark Website (www.fiberspark.com))
Started Oct 26, 2026, 11:33 AM UTC· resolved Oct 26, 2026, 11:36 AM UTC
- investigating Oct 26, 2026, 11:33 AM UTC
Fiberspark Website (www.fiberspark.com) is down at the moment. This incident was automatically created by Instatus monitoring.
- resolved Oct 26, 2026, 11:36 AM UTC
Fiberspark Website (www.fiberspark.com) is back up. This incident was automatically resolved by Instatus monitoring.
Minor October 19, 2026 www.fiberspark.com is back up 2m
Started Oct 19, 2026, 07:14 PM UTC· resolved Oct 19, 2026, 07:16 PM UTC
- investigating Oct 19, 2026, 07:14 PM UTC
Fiberspark Website (www.fiberspark.com) is down at the moment. This incident was automatically created by Instatus monitoring..
- resolved Oct 19, 2026, 07:16 PM UTC
Fiberspark Website (www.fiberspark.com) is back up. This incident was automatically resolved by Instatus monitoring..
Minor October 17, 2026 www.fiberspark.com is back up 8m
Started Oct 17, 2026, 09:31 AM UTC· resolved Oct 17, 2026, 09:39 AM UTC
- investigating Oct 17, 2026, 09:31 AM UTC
Fiberspark Website (www.fiberspark.com) is down at the moment. This incident was automatically created by Instatus monitoring..
- resolved Oct 17, 2026, 09:39 AM UTC
Fiberspark Website (www.fiberspark.com) is back up. This incident was automatically resolved by Instatus monitoring..