NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
We are still seeing this. I know the TOC was made aware of this issue two weeks ago, but despite all our servers being 0 seconds lagged on the NEXRAD2 feed tree, our data (from multiple providers who are also not lagged) is at least 10 minutes behind. Also, this page is a 500 internal server error and has been for months, and nobody has fixed it or seems to even notice: http://rtstats.unidata.ucar.edu/cgi-bin/rtstats/rtstats_topogif?NEXRAD2 And this one takes over a minute to load: http://rtstats.unidata.ucar.edu/cgi-bin/rtstats/rtstats_feedtree?NEXRAD2 ...but you can verify from the second link that we're not lagging (search for "tampa" or "chicago"). On Mon, Apr 28, 2014 at 7:33 PM, Blair Trosper < blair.trosper@xxxxxxxxxxxxxxxxxxx> wrote: > Am I crazy, or is anyone else seeing the 10+ minute lag on both feeds? > > It will occasionally come into sync, but then fall behind again. On one > of our servers that pulls the firehose of both, it's ingesting at 4.5 MB/s, > which is the highest I've ever seen. > > Perhaps an issue with NOAAPort or the data volume is too much for the NOAA > infrastructure? Or perhaps an issue with Internet2 itself? > > Then again, I might just be crazy, despite having excellent providers. > > ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ > ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ > Blair Trosper > Updraft Networks / Weather Data > NOC: 469-844-5440 > Early Watch Notifications: http://twitter.com/weatherwatches > -- ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ ∙ Blair Trosper Updraft Networks / Weather Data NOC: 469-844-5440 Early Watch Notifications: http://twitter.com/weatherwatches
ldm-users
archives: