Jan. 7th, 2022

solarbird: (Default)
We're down again, it's Comcast's fault again, as usual Tier 1 service bots are presuming we're idiots and it's our fault. So I wrote this on Twitter.



I got into an argument a couple of months ago with a guy who was Damned Well Sure that I had a zillion internet options that could meet our needs other than Comcast, and that he - in Montana, I think? - damned well knew that and I should STFU about infrastructure internet.

As I sit in my fourth major provider-caused outage since October, knowing we can't get an on-site tech from our provider for at least four days, having no idea if or when we might hear from Tier 2 to be sure we actually need one, I think on that, while talking again to providers.

We have Comcast, who we're with now.

We have HughesNet Satellite. 25mbps maximum down - about 15% of what we have - and negligible speeds up.

We have ViaSat Satellite. 100mbps maximum down - a mere 50% cut - and negligible speeds up.

We have Earthlink! It's DSL! But 75mbps. 43% of our current, though I have to say, infinitely more than the 0% we have right now.

But what I know _from experience_ is that the copper in this neighbourhood is nightmarishly bad, as in dropped calls on landlines bad, so hard pass.

We have a variety of cell phone companies, of course. That's how I'm online right now. Bandwidth isn't bad, but hoo boy the latency. I don't know if they offer fixed IP these days, but I guess I should check.

And we have Ziply. They're fibre. The numbers are fine and I go to the website and find that these days they're offering fixed IP services at last! Are we in business?

I look for pricing, and can't find it, so I use their chat to ask, and they can't tell me! Because the business services page links to consumer sales chat, not business sales chat, and they give me a phone number.

It's the wrong phone number.

So I go back to the website and find the right phone number, and I call it, and after some phone tree, I actually get to business sales. Yay!

And they tell me there's a greater than 10 minute wait to talk to BUSINESS SALES and I should use the website or call back later.

Think about that for half a second.

It's a >10 minute wait and I should call back if I want them to... _sell me service_.

And I just think about what that implies for support.

Mind you, I've been trying for an hour to get online @ComcastBusiness support to confirm that they've received the information I provided them and added to the latest outage ticket, so it's hard to imagine it being too much worse.

It's literally a matter of "Please confirm the above DMs describing our current situation have been added to ticket [number]."

It's been an hour. I'm resending the request every 10 minutes.

To be fair, they said they needed the account name and address too about 20 minutes in.

But I gave them that.

No response.

So, yeah. As I sit here trying to get support even to acknowledge the information I've sent, and as I sit contemplating being told to call back to be able to talk to _sales_, I think about how many, many choices we have.

As long as we choose for everything to suck.
solarbird: (Default)
Just tried to talk to Earthlink, in case they have fibre in our area yet and the evaluation services aren't aware of it.

After working my way through a _particularly_ nasty phone tree - seriously, who thinks fake typing sounds are a good idea - I reached someone.

It sounded like a Russian phishing sweatshop in there, for reals. I suppressed my laughter.

Ivan - or whoever - had to look up whether they offered fixed IP services on their business services, and came back after a reasonable period to confirm they did. So I gave him name and address and general requirements so he could look up our service location.

And he did some, and I was on hold for a couple of minutes, and he came back and said he would have to transfer me to his "Business people."

Except he answered on the "Business service" phone tree himself, and identified as that, so... that's fun. But I say okay.

Then I get a bit of hold music, and then SHARP METALLIC HORN NOISE RIGHT IN MY EAR, then more hold music, then a partial play of an recording that used the phrase "invalid transfer," and then I was abruptly disconnected.

So that went well.

We have all kinds of choices. As long as they all suck.

And again: this is the _sales_ experience.

Their support rating is _terrible_. I bet I can guess why.
solarbird: (Default)
Yeah. I tagged 'em. At this point, why the hell not?

SICK OF YOUR SHIT ROLL CALL:

1. "This isn't on our side, you should talk to your local IT about this."

A: It's been on your side EVERY TIME. Eventually, Tier 2 fixes it.

B: I AM THE LOCAL IT. I ran the WGA division server room at Microsoft. I HAVE SOME IDEA WHAT I'M DOING.

2. "Have you power-cycled your modem?"

Classic.

3. "Are you sure you have the right password?"

You reset it to factory default. Three times. It won't start magically working.

4. "Windows should be restarted."

My fleet of Linux servers glares at you angrily.

5. "I'll re-provision the modem. Wait five minutes and try again."

That didn't work the last four times, why is it going to work now? Oh look, it didn't.

6. "Someone will call you Monday."

[No call]

"Tuesday"

[Calls wrong number]

"Wednesday"

[Tier 2 shows up and fixes it]

(If we're lucky. I think the quickest we've been back up was two and a half days.)

7. Me: "[X] in Tier 2 told us you need to do exactly this, and can do that."

Tier 1: "We can't do that."

[tries again]

Tier 1: "All done!"

[nothing actually done]

8. [support wakes up from idle after hours of silence and apparent inactivity] “Is it fixed yet?”

No. No, as you have apparently done nothing, it is not fixed yet. The problem will not magically go away. It. Is. Not. Fixed. Yet.

Honestly, and I mean this in all sincerity, it has felt _many times_ like we've been being trolled.

Tier 2 is generally good to great and totally know what they're doing. Nice people.

Tier 1 - by phone and online - was not always a nightmare. I remember this. But it is one now.
solarbird: (Default)
After a couple of hours of trying, I finally got Tier 1 support to add the current situation to the current ticket. I did have to change the ticket number because they closed the original one without telling us, so that was great. And then they opened two others, one for tier 1 and tier 2. But in theory, this is on the tier 2 ticket now. Yay!

That's nearly two hours to get this text added to a ticket though. Jesus.

-----

The modem is not passing IPv4 packets across LAN to WAN. It _may_ be able to send IPv4 packets from _itself_ to the WAN, and it _can_ pass IPv4 packets from itself to the LAN, but it DOES NOT pass IPv4 packets _across_ LAN to WAN or (as far as I can tell) vice versa.

A simple test is using my laptop connected by wire directly to the modem, configured by the modem's DHCP. If I attempt to query your nameserver via IPv4 from this laptop, it _always_ fails. If I attempt to query your nameserver via IPv6 from this same laptop, it _always_ succeeds. See attached screencap.

The reason I believe the modem can talk IPv4 over the WAN is because if I use the built-in IPv4 ping functionality via the web interface, it reports success. Since it does so without details, I cannot be sure it's actually succeeding, as the administrative software is unreliable. But I suspect it's working.

However, any otherwise-identical attempt from the LAN side of the modem to use IPv4 pings to the same servers fail, 100% of the time.

The modem is showing other signs of IPv4 routing irregularities. I will describe one now:

If a laptop is connected to the LAN side of the modem with modem-issued DHCP address, pinging our fixed-IP machines on the same (LAN) side of the modem will sometimes work normally, sometimes succeed with great delay in ping issuance but _not_ response time, sometimes succeed with routing error complaints on some but not necessarily all packets, and sometimes (but rarely) fail outright, all within a few minutes of each other with no configuration changes.

The modem is showing other signs of irregular behaviour as well. I will describe the main one now:

The modem is sometimes refusing logins when given valid login credentials. If your support team resets the password to default, the default password will also not work, regardless of the number of resets.

I have discovered today that if one is attempting to login via the fixed IP (173.160.243.46) and it does not work, it will _probably_ work if one does exactly the same login attempt on the DHCP root address (10.1.10.1).

The same is also true in reverse. If login via the DHCP root address (10.1.10.1) is failing, trying exactly the same login via the fixed IP (173.160.243.46) will _probably_ work.

If there is a reasonable explanation for this behaviour other than modem failure, I am not seeing it.

For these and other reasons, I am strongly suspecting that the modem is not taking provisioning properly, regardless of what it is reporting. The only reprovisioning from your side that I have seen have any effect at all is a full factory reset from remote. (My attempt to do a factory reset via the front panel failed - as in, didn't seem to work at all - and as this was when it was refusing all logins, I could not try via the customer administrative access panels.)

At this point we are down for just short of 24 hours and we yet again request escalation to Tier 2. Tier 1 have demonstrated yet again that they are NOT CAPABLE of solving this problem, and this is our fourth major network outage caused by your side since October, all previous lasting between 2 and 5 days, this one so far only 1 day.

The ticket number, again, is [deleted]. Please add all of the above to the ticket. Thank you.
solarbird: (Default)
The photos are gone because fucking Comcast Business keeps taking us offline and can't get us online again for days every time they do it.

The photos will be back when Comcast Business takes its boot off our connectivity's neck again.

May 2025

S M T W T F S
    123
45678 9 10
1112 13 14151617
18192021222324
25262728293031

Most Popular Tags

OSZAR »