jlgaddis: ah ok, good point. tnx
up_the_irons: yeah I second that.
eg the other day I reported an ipv6 outage to my work's ISP.
after two premature closes ("it's fixed" "no it isn't, did you even check?") I pointed out that there was a routing loop.
then they finally fixed it.
"So, uh, what happened?"
hahahaha
"It looks like there was a routing loop."
"did you even check" LOL
... so any actual explanation of what went wrong = A++++++++++++++ WOULD... UH... [VERB] AGAIN.
yeah
another good poing, tnx
*point
up_the_irons: I'd find incident reports interesting. I appreciate the openness
plett: roger
you wouldn't necessarily have to share them with *everyone*, but as someone who is affected it's nice to hear what happened/what you did/what you're gonna do to mitigate the chances of it happening again
and that's not just you, that's anyone that i pay for a service
be glad you're not my transit providers  =)
jlgaddis: yeah makes sense
http://slashdot.org/topic/datacenter/terabit-ethernet-is-dead-for-now/
wow it's 3am already
meh, 400 gbps will get about as much interest as 40 gbps did
cheaper to just do 4x10gig in a lag
10 gigabit to the desktop
gogogo
indeed
any chance someone could check the new customer queue? I'd <3 you forever.
up_the_irons: ^
milki:  beeping staff?