We had a contractor accidentally dig through our main fiber line near downtown last Tuesday... I was always told to trust the backup circuit but now I see why you need more than one failover. Has anyone else had a single point of failure come back to bite them?
I was at a data center off LaGrange Road in Frankfort, and this older guy named Tom from the NOC was reaming me out because I left a dust cap off a LC connector on a patch panel. He pulled me aside and showed me the dB loss on his OTDR, it was like 2.8dB worse than it should have been because of one microscopic speck of crud. I laughed it off at first but now I double check every single connector before I plug it in. Anyone else run into a stickler for cleanliness who actually taught you something?
Spent 45 minutes digging through old emails to find the secondary provider credentials because the guy who set it up left two years ago, has anyone else dealt with a single point of failure like this?
I was looking at getting fiber to my shop out in a rural area near Phoenix. Cox told me $18k to run it 3 miles from the nearest junction. I found out from a county permit filing that they already had fiber running right past my property for a cell tower they put in 2 years ago. Anyone else ever had an ISP try to charge you for existing infrastructure?
After three years of fighting with a shared cable connection that would tank every afternoon, we finally got a quote from a local enterprise ISP in Dallas for a symmetric 500Mbps fiber circuit at $800 a month, and 6 months in it's already paid for itself in saved productivity, has anyone else made the switch from shared to dedicated and seen a similar jump?
Last Tuesday night our primary fiber link went down at 2 AM. Comcast couldn't send a tech until 10 AM even though we pay for 4 hour SLA. I had to failover to our backup DSL line at 50 Mbps for 500 users. Has anyone else had luck negotiating better response times with big carriers?
Had our primary ISP link go down Tuesday morning at 3am for our Chicago office. The monitoring system showed green the whole time because the backup circuit was carrying traffic. I didn't find out until I got in at 7 and noticed latency was junk. Called the ISP and they said the fiber was cut by a construction crew at 2:45am and nobody bothered to check the backup was saturated. Has anyone else had a monitoring stack fail to flag a failover situation?
We had a Megaport connection for our Phoenix office that was okay but nothing special. Latency to AWS was around 15ms and we got packet loss at peak hours every other week. About 6 months ago we switched to direct peering with Level 3 and a local data center. Our latency dropped to 2ms and that packet loss issue vanished completely. Has anyone else seen that big of a jump just from changing the type of connection?
I keep seeing teams sign multi year fiber deals without checking what happens if the local loop provider changes terms mid contract. Just last month my company in Portland got hit with a 15% rate hike from the last mile provider because we locked into a 5 year deal with a big ISP but didn't secure the local loop pricing separately. The sales rep literally said "oh yeah that's between you and the LEC" when I asked about it after the fact. Now we're stuck paying extra or breaking the contract for a penalty. How do you guys handle this when negotiating enterprise contracts? Do you always split the local loop and transport into separate agreements?
I was at a client site in Phoenix last week checking their network closet before a big switchover. The datacenter guy there told me he tags every fiber patch cable with a printed label on both ends after he saw a tech pull the wrong one and take down 3 floors of users. I started doing the same thing on my commercial jobs and it's cut my trouble call time in half. Anyone else got a small habit like that from watching someone else's mistake?
So I'm sitting at this place downtown, trying to get some paperwork done, and this guy next to me is on the phone telling someone that enterprise fiber is basically "plug and play" and you just need to call the provider and they handle everything. I almost choked on my drink. I manage a building with 40+ units and we had a fiber install that took 6 months because of conduit issues, permitting with the city, and the vendor sending the wrong termination equipment twice. Has anyone else had a client or tenant completely underestimate what it takes to get real fiber lit up in a commercial space?
Was going over our ISP contract renewal last week and noticed our rate per meg is way higher than what a buddy pays three blocks away. He leases in a big office complex and I'm in a standalone building. Called around and the sales guy flat out said smaller buildings don't get the same deals because they lack competition on the fiber run. Anyone else in a small office get hit with this pricing gap?
I've been running a small business on a carrier-grade NAT setup for 18 months now in Chicago and honestly haven't had the horror stories people keep warning about. We use a free dynamic DNS service and a cheap VPS tunnel for the one server that needs direct access. Has anyone else actually tried working with CGNAT instead of fighting it?
I was banging my head against a wall for weeks trying to fix packet drops on a regional MPLS link between Dallas and Houston. The engineer at our carrier took one look at my pings and said "dude, your average latency is fine but your jitter is all over the place, you need to check your buffer settings." Has anyone else had a similar issue where the obvious metric wasnt the real problem?
I signed a 3-year deal with FiberConnect Midwest last March because their sales guy swore they had enterprise-grade reliability. Lost 12 hours of connectivity in the first month alone and their support blamed my own equipment every time. Has anyone else fought these contract exit fees and actually won?
For the last 8 years I was running our small office on a single fiber connection from Comcast, 500 down 50 up. We had one outage in July 2023 that lasted 4 hours during a client demo and I lost a $12k contract over it. So I added a secondary ISP from a local provider, 200 down symmetrical, and set up BGP with our firewall. Now if one goes down the traffic shifts in under 30 seconds. Has anyone else made the jump to multihoming and seen a real business impact from it?
We were paying through the nose for enterprise fiber from Comcast Business and still getting 3 second load times on our main site. Tried route optimization, tried peering agreements, nothing stuck. Then our network guy noticed our BGP was advertising 20+ routes to the same IP block. Consolidated it down to 3 paths and it was like flipping a switch. Has anyone else seen junk route tables kill performance?
I was standing in front of 50 people at the Windy City ISP Summit last Tuesday showing off our new peering setup when my router decided to flap the session three times, and I had to pretend it was a planned failover test while frantically SSHing from my phone under the podium. Has anyone else had a public demo go sideways like that?
For years I figured all these enterprise ISPs bragging about fiber were just puffing up their sales pitch. Seemed like the same copper lines with a fresh coat of paint. Then last month I had a job in a mixed-use building down in Nashville where the ISP ran actual single-mode fiber right into the comms closet. During a pipe burst my guys soaked a patch panel, and the ISP tech rolled out at 2 AM, swapped the SFP, and we were back online before the plumber even got there. That response time alone convinced me fiber isn't just for the big data centers. But now I'm wondering if that level of service is standard or just a Nashville fluke. Anyone else get burned by a so-called enterprise ISP that sold fancy gear but delivered nothing special?
I was training a new guy on our main account setup process, and I mentioned the old 5-year, iron-clad contracts we used to push. He just looked at me and said, 'You guys actually signed those? That's like buying a car without test driving it.' It hit me because he's right, that was the standard for so long (I remember a 2012 deal for a 100 Mbps line in Phoenix that locked us in for half a decade). Now everything is about month-to-month flexibility and cloud-based failover. It's wild how the whole mindset shifted from 'lock it down forever' to 'be ready to switch next month.' Makes you wonder what the next big shift will be. What's the shortest contract term you've been able to get a decent enterprise circuit on lately?
We had that old 1.5 Mbps T1 for years, handling about 30 users and our basic phone system. Last year, we switched to a 100 Mbps fiber circuit from the same provider for roughly the same monthly cost. The difference wasn't just speed; video calls stopped freezing, and file transfers that took 10 minutes now finish in seconds. What's the biggest jump in service you've seen that actually changed how your team works?
Cost about $1,200, but it caught a weird voltage sag last week that would have taken out our primary router. Anyone have a recommendation for a more affordable model for a smaller branch location?
They had a full redundant path from a different provider that kicked in before their monitoring dashboard even finished sending the alert email. I've been burned by paper SLAs before, but this one in Denver actually paid out the service credit without us having to fight for it. Has anyone else had a provider's disaster recovery plan work exactly as advertised?
Has anyone else found a good way to automatically flag internal network events on ISP performance dashboards before a customer calls?
Went with the longer term for stability, but now I'm seeing new fiber options pop up. Anyone else locked into a contract and feeling stuck?