![]() ![]() ![]() |
|
This issue is still unresolved for the customer I'm dealing with. They haven't been able to print invoices all day. Spark gave me an updated ETA of 5pm. This is the kind of thing that should be published on the Spark network status page.
Still not working for my customer. Nothing on the outage page but when I rang the small business helpdesk there was a recorded messages advising there was a problem with the fibre system and they were working on it.
Agreed, if someone from Spark is reading this, it would be great to show this thread to your comms team.... basically if I go to the outage map and there is no info about an issue I assume it is my fault and waste a whole lot of time attempting to troubleshoot....
Are you guys having problems with your static IP address not being correctly allocated?
I emailed this address and that is how I got it sorted;
Might be worth a go if that is the issue for you.
the restoration is happening on a rolling scale.
Late last night this should be resolved. If there are isolated cases please do let us know :)
As for outage map, I'll pass the feedback along. There is a bit of work going into this space.
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
This sounds like what happened to us just before easter - all of our UFB static IPs changed with no notice from Spark. Really fun updating firewall configs, site to site VPN, DNS, etc right a couple of hours before the long break.
Ended up being that our plans were changed to "new plans" (despite us being on Voice Connect so no need). Wasn't too happy with our account manager after that one.
Peppery:
This sounds like what happened to us just before easter - all of our UFB static IPs changed with no notice from Spark. Really fun updating firewall configs, site to site VPN, DNS, etc right a couple of hours before the long break.
Ended up being that our plans were changed to "new plans" (despite us being on Voice Connect so no need). Wasn't too happy with our account manager after that one.
Different cause here, very frustrating situation for those that manage these systems though..
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
|
![]() ![]() ![]() |