Welcome • User Guide
ToS • Privacy • Canary
Donate • Bugs • License

©2025 Poal.co

My oh my!

facebook.com still down for 4.5 hours so far.

My face is smiling with so much joy and pride over this unbelievable achievement (of others)

= = = = = = = =

= = = = =

STATUS UPDATE 5:00 EST! DOWN still for DNS and its a big deal!

Facebook DATA will be fine, a little birdie told me, its the DNS still down from a three component exploit attack that should have lasted merely 10 minutes.

There's still no connectivity to Facebook's DNS servers:

> traceroute a.ns.facebook.com
  traceroute to a.ns.facebook.com (129.134.30.12), 30 hops max, 60 byte packets
  1  dsldevice.attlocal.net (192.168.1.254)  0.484 ms  0.474 ms  0.422 ms
  2  107-131-124-1.lightspeed.sntcca.sbcglobal.net (107.131.124.1)  1.592 ms  1.657 ms  1.607 ms 
  3  71.148.149.196 (71.148.149.196)  1.676 ms  1.697 ms  1.705 ms
  4  12.242.105.110 (12.242.105.110)  11.446 ms  11.482 ms  11.328 ms
  5  12.122.163.34 (12.122.163.34)  7.641 ms  7.668 ms  11.438 ms
  6  cr83.sj2ca.ip.att.net (12.122.158.9)  4.025 ms  3.368 ms  3.394 ms
  7  * * *
  ...

So they're hours into this outage and still haven't re-established connectivity to their own DNS servers.

"facebook.com" is registered with "registrarsafe.com" as registrar. "registrarsafe.com" is unreachable because it's using Facebook's DNS servers and is probably a unit of Facebook. "registrarsafe.com" itself is registered with "registrarsafe.com".

Almost 5 hours with no working "a.ns.facebook.com" !!!

Bwah hah hah hah!!!

Circular interdependencies caused by MINORITY HIRE TOKEN SHEBOONS in IT at FACEBOOK!?

Thanks, La'Quisha! (No its not specifically a person named "La'Quisha" that allowed the circular authentication defect and bad TTL cache reset times)

BGP attack was one third the attack... by the end of this week, some more revelations may unfold.

My oh my! **facebook.com still down for 4.5 hours so far.** My face is smiling with so much joy and pride over this unbelievable achievement (of others) ===== = = = = = = = = = = = = = STATUS UPDATE 5:00 EST! DOWN still for DNS and its a big deal! Facebook DATA will be fine, a little birdie told me, its the DNS still down from a three component exploit attack that should have lasted merely 10 minutes. There's still no connectivity to Facebook's DNS servers: > traceroute a.ns.facebook.com traceroute to a.ns.facebook.com (129.134.30.12), 30 hops max, 60 byte packets 1 dsldevice.attlocal.net (192.168.1.254) 0.484 ms 0.474 ms 0.422 ms 2 107-131-124-1.lightspeed.sntcca.sbcglobal.net (107.131.124.1) 1.592 ms 1.657 ms 1.607 ms 3 71.148.149.196 (71.148.149.196) 1.676 ms 1.697 ms 1.705 ms 4 12.242.105.110 (12.242.105.110) 11.446 ms 11.482 ms 11.328 ms 5 12.122.163.34 (12.122.163.34) 7.641 ms 7.668 ms 11.438 ms 6 cr83.sj2ca.ip.att.net (12.122.158.9) 4.025 ms 3.368 ms 3.394 ms 7 * * * ... So they're hours into this outage and still haven't re-established connectivity to their own DNS servers. "facebook.com" is registered with "registrarsafe.com" as registrar. "registrarsafe.com" is unreachable because it's using Facebook's DNS servers and is probably a unit of Facebook. "registrarsafe.com" itself is registered with "registrarsafe.com". **Almost 5 hours with no working "a.ns.facebook.com" !!!** ========== Bwah hah hah hah!!! Circular interdependencies caused by MINORITY HIRE TOKEN SHEBOONS in IT at FACEBOOK!? Thanks, La'Quisha! (No its not specifically a person named "La'Quisha" that allowed the circular authentication defect and bad TTL cache reset times) BGP attack was one third the attack... by the end of this week, some more revelations may unfold.

(post is archived)

You are currently inside a comment thread.
Click here to see all the comments (12).
[–] • 1 pt

I hope that's not your IP address in the trace.

[–] • 1 pt (edited )

No. I am not a newb. Its not even a trace remotely related to me in any universe, but it is real.

If I showed you my real traces , including the path to this site I am typing on now, AOUs jaw would drop with the 12 spurious ADDITIONAL fed spook intermediary spy machines between this 'infested' home residential router I am using this month for this specific site, being probed by 12 extra hops VISIBLE, out of a total of 28 hops on merely the SIDE FROM THE VISIBLE HOME ROUTER to poal.co. After I start using this site and a couple others, bewtween 1 to 3 extra new redirect hops appear, this time 10 unneeded packet hops. In older years the extra fed hops actually went hundreds of miles back and forth to VIRGINIA!!!! Now they are all redirects to local in-state feds. Sometimes my BACKBONES were swapped for just my pathways on routers I infest after a few days. I prefer to not soly rely on commercial VPN out of paranoia, and use 4 laptops like an insane weirdo, when on the road, one locked in a metal security case.

The hops from the opaque side on the OTHER side of the router go through various VPN selections.

anyways, in summary

I guess some glowniggers like to spend a lot of time watching and listening to me.

Its been the story of my life for decades, non-stop.

[–] • 0 pt

Interesting. I did the same thing here. It's essentially my ISP and their backbone ---> Level 3 ---> host

[–] • 0 pt

Everyone's packets get middled. Not just yours.