cyclicflux: afraid.org cyclicflux: I like and recommend http://dns.he.net Hey guys. New website? redesigned a few weeks ago, yea Like it. Much cleaner. cyclicflux I like ZerigoDNS. They also have a public API. I happened to write the Python client ;)~ (no affiliation though) pjs: seconding zerigo. their api is a little annoying to use, but it works. jdoe, Yea it is slightly annoying. Oh well. I wrote the Python API client to easily integrate it into a product deploy process.. Works perfectly for us I just wrote a ghetto little shim to update a 'dyndns' record in perl. Should ... try to write something real for it. meh. it's quitting time. night man did all sites just die? holy packet loss batman yes losing 98% of packets thats not a good statistic between level3 and packet exchange, afaict retard customer getting ddos'd? or upstream being retarded? =) who knows but this is bad..... ugh Bah. at least it isnt just me webhostbudd: lag to your server? dpn: yes, extreme packet loss on the phone with GTT NOC. Can't reach my out-of-band gear, so I can't see what is happening from the "inside" They are having a line card issue GTT? GTT bought PacketExchange gotcha oh, it appears I can get in from my devio.us shell, nice of those that can access their gear, has the packet loss subsided? (it looks better now) looks like it i'm debating shutting off the GTT peer until w/e they broke is fixed if it's packetexchange, i'm going through there and not seeing any problems yeah, it's PE it's still unreachable for me 8. TenGigabitEthernet1-2.ar5.LAX1.gblx.net 0.0% 2 26.7 22.8 18.9 26.7 5.5 9. ae2-40G.scr4.LAX1.gblx.net 0.0% 2 11.8 12.0 11.8 12.3 0.4 10. po2.ar4.LAX1.gblx.net 0.0% 2 20.1 20.1 20.1 20.1 0.0 11. ??? bah, what a bad paste 11 ae-3-80.edge3.losangeles1.level3.net (4.69.144.137) 85.894 ms 12 cr1.lax1.us.packetexchange.net (4.71.136.2) 94.239 ms 13 ge0-arpnet.cust.lax07.mzima.net (67.199.135.102) 97.748 ms all the packet loss i was seeing earlier was on hop 12 seems to be fine now though i'm seeing bad packet loss again hum, it's down? me too, different path this time though going through savvis now geez, routing clusterfuck in socal =) bad news bears things are looking up FINALLY, it appears PE shutdown the broken GBLX peer now I can reach my stuff from home on primary network maybe they saw my tweet ;) heh, can you send communities to packet exchange? yeah, but since it has gone through 3 owners up to now, I am never sure which communities are still working or, more specifically, "per-upstream" communities... e.g. tag your prefixes with a community saying "don't advertise this to gblx"? heh Mzima -> PE -> GTT oh, right