Forum Discussion

MarkJFine's avatar
MarkJFine
Professor
6 years ago

More evidence that CenturyLink is broken

I have a bot that runs three times a day at 7, 9:45, and 12 noon that pulls an RSS feed for the website I administer, embeds the last 10 article titles onto an image and posts that image to the site's Twitter account.

 

Two days ago one of those instances got a timeout while waiting for an oauth authentication with Twitter and failed. Immediately following that I manually logged in and was able to run the Twitter portion of the bot manually without error.

 

Yesterday, all three went fine.

 

Today, only two of those instances failed for the same timeout during oauth. I just logged in and ran fine manually.

 

Twitter's backbone is Cali is <drumroll> Level3/CenturyLink

 

Folks... all of this can't possibly be coincidence.

general discussion is not a support area
  • MarkJFine's avatar
    MarkJFine
    Professor
    6 years ago

    Incidentally, just had a disturbing Twitter exchange with their social media 'help'... bottom line: they wouldn't do anything without a DM.

     

    Doubtful they would have checked into anything anyway, since I don't have an account with them.

  • gaines_wright's avatar
    gaines_wright
    Tutor
    6 years ago

      I've been doing a lot of expermenting  with traceroute today.  I'm just sort of stumbling around in the dark with this.  One of the thngs I've discovered is that the first 6 entries seem to be the same no matter where I'm tracing to:

     

    1 192.168.42.1 (192.168.42.1) 0.223 ms 0.236 ms 0.274 ms                                                          //  Hughes router
    2 100.67.205.153 (100.67.205.153) 0.905 ms 1.016 ms 1.169 ms                                                  //   Shared address 
    3 dpc6935186182.direcpc.com (69.35.186.182) 589.663 ms 589.681 ms 589.643 ms                  //   Hughes site
    4 dpc6935188058.direcpc.com (69.35.188.58) 1369.224 ms 1369.243 ms 1369.193 ms              //   Hughes site
    5 ae13-575.edge3.Denver1.Level3.net (4.28.103.141) 1369.171 ms 1369.150 ms 1369.125 ms  //  CenturyLink

    6 * * *

      The text after the C++ style comment is what I've  been able to discover about the address so far.   When CenturyLink appeared I remembered your post. 

    • MarkJFine's avatar
      MarkJFine
      Professor
      6 years ago

      Yes. So this is what you're looking at:
      1. Your wifi/router, sometimes these show your public IP depending upon the tracert options. Not sure why the modem itself (192.168.0.1) doesn't show.

      2. Gateway input from satellite

      (not sure why it's showing a shared IP on yours, should be something in 69.35.184.0/21 like the other two)

      3. Gateway processing

      4. Gateway output to internet (may vary)

      5. Upstream provider to gateway

      6. [is always obfuscated by ICMP blocking for some reason on CL, but should be the provider's backbone]

      ...

      all the other nodes to the target address.

      • gaines_wright's avatar
        gaines_wright
        Tutor
        6 years ago

        Thanks for the info.   I guess the differences may be caused by my use of the Linux version of traceroute.