GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE
  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Conversation

Notices

  1. Embed this notice
    Bill Woodcock (woody@pleroma.pch.net)'s status on Friday, 23-Feb-2024 07:20:01 JST Bill Woodcock Bill Woodcock
    • Kevin Beaumont
    @GossiTheDog

    Uh... What evidence do you have that it had to do with peering?
    In conversation about a year ago from pleroma.pch.net permalink
    • Embed this notice
      Bill Woodcock (woody@pleroma.pch.net)'s status on Friday, 23-Feb-2024 07:41:34 JST Bill Woodcock Bill Woodcock
      • Kevin Beaumont
      @GossiTheDog

      That doesn't explain reorders on PRI trunks, nor does it explain AT&T mobile-to-mobile calling being down.
      In conversation about a year ago permalink
    • Embed this notice
      feld (feld@bikeshed.party)'s status on Friday, 23-Feb-2024 07:42:14 JST feld feld
      • Kevin Beaumont
      @GossiTheDog That's stupid, why would the CEO be responsible for a BGP change?
      In conversation about a year ago permalink
    • Embed this notice
      Bill Woodcock (woody@pleroma.pch.net)'s status on Friday, 23-Feb-2024 07:48:23 JST Bill Woodcock Bill Woodcock
      • Kevin Beaumont
      @GossiTheDog

      The CNN article also only cites one anonymous source for that, and doesn't say that the source actually has any inside knowledge.

      Again, if you can posit a causal link between anything to do with peering, and the observed failures, I'm all ears.

      Until then, canonically, it was the DNS.

      No, just kidding. For once, I don't think there's any plausible link with the DNS either.
      In conversation about a year ago permalink
    • Embed this notice
      Bill Woodcock (woody@pleroma.pch.net)'s status on Friday, 23-Feb-2024 07:58:50 JST Bill Woodcock Bill Woodcock
      • Kevin Beaumont
      @GossiTheDog

      The Optus outage was indeed iBGP, and it affected the underlying data routing across their network. That was visible in their Internet service. Have you seen any reports of AT&T fixed broadband having been affected? If it had anything to do with peering, that would also have been down. The fact that AT&T was urging affected customers to switch to "wi-fi calling" and that that was mostly working, would seem to indicate that there were not problems on the data network. That some "wi-fi calls" were not going through can be attributed, like the people complaining to T-Mobile and Verizon, to people trying to reach AT&T mobile customers.

      Again, I don't yet have a theory that I believe holds water, I'm just trying to rule out things that appear to be contradicted by the facts as reported thus far.
      In conversation about a year ago permalink
    • Embed this notice
      Bill Woodcock (woody@pleroma.pch.net)'s status on Friday, 23-Feb-2024 08:02:10 JST Bill Woodcock Bill Woodcock
      • Kevin Beaumont
      @GossiTheDog

      If it was white-labeled from another provider?
      In conversation about a year ago permalink
    • Embed this notice
      Bill Woodcock (woody@pleroma.pch.net)'s status on Friday, 23-Feb-2024 08:21:02 JST Bill Woodcock Bill Woodcock
      • Kevin Beaumont
      @GossiTheDog

      Explain?
      In conversation about a year ago permalink
    • Embed this notice
      Future Sprog (futuresprog@mastodon.nzoss.nz)'s status on Friday, 23-Feb-2024 08:26:48 JST Future Sprog Future Sprog
      in reply to
      • Kevin Beaumont

      One or both of you have server clock issues.

      You’re chatting backwards and forwards through time.

      Can the one in the future please tell us the answer from AT&T because I was betting on Cyber Squirrel.

      @woody @GossiTheDog

      In conversation about a year ago permalink

      Attachments


      1. https://mastodon.nzoss.nz/system/media_attachments/files/111/977/689/009/977/617/original/c1504ee16ef1403e.jpeg
    • Embed this notice
      fireshaper :lpuverified: (fireshaper@locksport.space)'s status on Friday, 23-Feb-2024 09:30:27 JST fireshaper :lpuverified: fireshaper :lpuverified:
      • Kevin Beaumont

      @GossiTheDog I heard from someone in the telco field that it was due to a bad update for the leap year.

      In conversation about a year ago permalink

Feeds

  • Activity Streams
  • RSS 2.0
  • Atom
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.