up_the_irons: kill all the /24s? shit is about to get real lol pyvpx: actually i'm adjusting the tcam distribution so i can do 768K routes. should suffice for a while. man I was just talking to folks last month "I need to setup a FIX MAH TCAM" website for when 512K apocolypse hits and here it is too fast for my lazy ass hahahaha might as well throw one of the numerous domains I've hoarded over the years and throw a landing page up can't hurt right right Oh look, it was Verizon all along, just as I'd joked :D http://www.bgpmon.net/what-caused-todays-internet-hiccup/ hah brycec: lol nice where does it show your current data transfer amount? like total you have assigned for your VPS/account portal.arpnetworks.com i dont see where it says where your total transfer is tho i think if you click on your svc name it should show you up_the_irons: thanks for that -w option on mtr :) m0unds: Doesn't tho. =/ is there a link to cacti there? under services yes but that doesn't show you like Used: this much, of Allowed This much: just shows how much you use, not what you have to use. ah I see what you mean under "My Services Summary" I see forgotten: look at the "Commit" column in the Portal. it'll say like "500GB" it doesn't show what you "have left", it's true Awwww!!! bingo! up_the_irons: ty! :) :) anyone know the ASN of the The Canadian Bitcoin Hijack from a few days ago? http://www.bgpmon.net/the-canadian-bitcoin-hijack/ << they dont list it explicitly >> http://www.secureworks.com/cyber-threat-intelligence/threats/bgp-hijacking-for-cryptocurrency-profit/ http://mailman.nanog.org/pipermail/nanog/2014-August/069131.html appears to give an example as-path from when a prefix was hijacked meingtsla: thanks, would it be the last entry in that ASPATH? I believe so The path goes like HE.net, Ontario(Canada), Bulgaria, France, Austria, California (US) the Ontario ISP seems to be the responsible party in this case Montreal rather you can solve the bgp hijacking problem with a blockchain forget RPKI doa imo gl implementing that up_the_irons: if you kill all /24 wouldnt a lot of Anycast prefixes just stop working correctly? 8.8.8.0/24 and 8.8.4.0/24 come to mind mnathani: no, the traffic would just take the default route up_the_irons: I thought that would only happen if there was no matching route, but wouldn't most /24s be covered by an overlapping route like : 8.0.0.0/9 which would be most specific if the /24 was not in the table? sure, if a more specific route exists, then that one is taken so in this case the traffic would go to level3 while it actually needs to get to Google for destination: 8.8.8.8 and then level3 would hand it off to Google b/c they would have the /24 :) it's a longer path, but still a working one hence sub-optimal routing if you can't take a full table but that is becoming more the norm these days with the full routing table getting so large right