Thanks for the response Chris. I should not have used the word "provider" when speaking of NASA. All the traceroutes I have done show hand-off from your company though. For example: 9 193.ATM4-0.BR2.SJC1.ALTER.NET (152.63.51.181) [...] 13 border.hcn.hq.nasa.gov (198.116.63.2) 14 realhq.hq.nasa.gov (198.116.66.254) and 10 POS6-0.BR3.DCA6.ALTER.NET [152.63.38.117] [...] 14 border.hcn.hq.nasa.gov [198.116.63.2] 15 realhq.hq.nasa.gov (198.116.66.254) BTW folks are interested, but there is little data coming in to share. As time goes on, I hope folks that show unusual traffic levels (on both sides; eyeball networks and content networks as well as transit networks) will send pointers to me that I can share with others. I am very interested in flash crowd situations and how to mitigate the problems associated with them... scott On Sat, 1 Feb 2003, Christopher L. Morrow wrote: : : : On Sat, 1 Feb 2003, Scott Weeks wrote: : > Hello, : > : > I write this to ask network operators to share your statistics of this : > flash crowd with NANOG. : > : > For example, if possible, could NASA folks let us know the peak and : > average hit rate to NASA TV (rtsp://198.116.66.254) or the traffic rates : > on the routers leading into this server? (border.hcn.hq.nasa.gov and : > realhq.hq.nasa.gov) : : This sounds like fabulous data to see. : : > : > Similarly, for UUnet folks (as you're the provider) or anyone that has : > collected statistics that they're willing to share. : > : : Unfortunately UUNET doesn't provide connectivity to this, except for UUNET : customers, NASA is not a direct customer... : : > Graphical (MRTG-esq) would be the best. If folks don't want to hear about : > this, I'll take any info privately and summarize to anyone that asks me. : > : > Thanks, : > scott : > : :