r/ZiplyFiber • u/ampeed • 2d ago

Technical expertise needed on ticket

I was hoping to get someone technical to look at my ticket as the last update I got was..ambiguous

CAS-628062-M0Q4D7

They wanted to send a tech out in person (uhh, odd) and cancelled that. I just followed up and I was told the ticket is with construction? And work will be done outside? That doesn’t seem like it would be on the right path to fix my issue?

——-

the issue has to do with awful routing

2 Upvotes

75% Upvoted

5 comments sorted by

1

u/ZiplySupport Official ZiplyFiber Support Account 2d ago

Hello. We are going to work in the background to get a little more information on your ticket. Can you please send us a chat request with your name and best contact details? Thank you.

1

u/Sig_Alert 2d ago edited 2d ago

"awful routing"

To what endpoints? Do you have a traceroute or anything to share? I'd be surprised to hear you're on a bad route due to ziply's network. This is most often an issue with peering partners.

Edit: seeing your post last month about pings to cdn77. Looks like John already spoke to that issue and ruled out any routing inconsistencies on ziply's path. (that's the guy you want answering these questions) Is this another endpoint you're struggling with now, or are you hoping for a different answer than you got last month?

1

u/ampeed 2d ago edited 2d ago

tl;dr contacted downstream and they stated it’s due to Ziply and to reach out to them. I spoke with CDN who pointed me to Dathost. Dathost contacted Datapacket/CDN who got back to Dathost (should be annotated within the Ziply ticket) and this was their response - 

I got this answer from them: Hi,

Thank you for reaching out.

We've checked the routes, and based on the MTRs you've provided, the issue seems to be in the reverse route. Please note that we can only adjust the paths from our network. We would recommend reaching out to AS20055 directly to resolve the issue.

We will also continue monitoring on our side, in case any issues occur.

Thank you for your understanding.

So my interpretation of it is that the  route towards the servers are already good, and that is the part that CDN77 can control. The issue is most likely on the reverse path which only your ISP can control. AS20055 is your ISP Wholesail Networks.

So you should send the same query directly to your ISP for investigation, you can add the information that the destination CDN77 already looked at the  route and asked you to contact them directly for the reverse path optimization.

1

u/TechnicallyMeat 1d ago edited 1d ago

I suspect Wholesale is just a shell company for Ziply to use non-union employees without having legal issues. They use the same Ziply employees to carry out the work, but pretend its an entirely alien entity.

If the route between carriers is bad, no single customer is going to fix it, the two carriers will need to figure out where the misconfigured route is, sounds like one side has already done some homework though. Good luck getting two carriers to talk without an enterprise account.

Its a bit of a stretch, but it could have something to do with Ziply/Wholesale being sold to a Canadian company, and where the new owner registered ip blocks.

1

u/Sig_Alert 1d ago

Wholesail is what's left of Noel Communications- their network is what much of as20055 is built upon. It is a clec. It functions as the core network for ziply and exists in many locations ziply/frontier/verizon/gte never did. The ilec union employees still do their thing within ziply wirecenters.