NCDC Disappears

Posted on May 10, 2014 by Tony Heller

ScreenHunter_334 May. 10 14.47

Google Chrome could not find www.ncdc.noaa.gov

About Tony Heller

Just having fun
This entry was posted in Uncategorized. Bookmark the permalink.

17 Responses to NCDC Disappears

  1. GeologyJim says:
    May 10, 2014 at 9:07 pm

    Inconvenient facts must be removed and purged from history

    Reply
  2. _Jim says:
    May 10, 2014 at 10:14 pm

    The website “Is it down right now” which has the URL for this check:

    . . . . http://www.isitdownrightnow.com/ncdc.noaa.gov.html

    Titled:

    . . . . “Ncdc.noaa.gov Server Status Check”

    reports the following:

    Website Name: . . . . National Climatic Data Center
    URL Checked: . . . . http://www.ncdc.noaa.gov
    Response: . . . . . . . no response
    Time: . . . . . . . . . . ~1 day

    – – – –

    McCoy says: “It’s dead Jim”

    Reply
  3. Ben Vorlich says:
    May 10, 2014 at 10:39 pm

    It’s back again now.

    Reply
  4. _Jim says:
    May 10, 2014 at 11:31 pm

    Looks like it dies deep into the govt server farm complex:

    – – – – – – –

    Tracing route to vlb.ncdc.noaa.gov [205.167.25.100]
    over a maximum of 30 hops:

    1 1 ms 1 ms <1 ms 192.168.1.7
    2 12 ms 11 ms 13 ms xxxxxxxx [xx.xx.xxx.xx]
    3 11 ms 11 ms 15 ms **.**.**.***
    4 33 ms 35 ms 35 ms gar19.attga.ip.att.net [12.122.117.49]
    5 * * * Request timed out.
    6 59 ms 53 ms 53 ms rtpcrs-gw-to-chltcrs-gw.ncren.net [128.109.212.1
    ]
    7 * * * Request timed out.
    8 * * * Request timed out.
    9 47 ms 49 ms 49 ms xe-7-2-0-0.clpk-t640.maxgigapop.net [206.196.178
    .89]
    10 56 ms 55 ms 58 ms noaa-rtr.maxgigapop.net [206.196.177.118]
    11 55 ms 57 ms 66 ms 140.90.111.46
    12 58 ms 60 ms 62 ms 140.208.63.29
    13 * * * Request timed out.
    14 74 ms 74 ms 76 ms 205.167.25.226
    15 72 ms 72 ms 74 ms 205.167.25.225
    16 76 ms 76 ms 72 ms 205.167.25.234
    17 * * * Request timed out.
    18 * * * Request timed out.
    19 * * * Request timed out.
    20 * * * Request timed out.

    Reply
  5. Andy Oz says:
    May 11, 2014 at 12:23 am

    Hi Steven,

    Just found this when I was ferreting around. “This day in Weather History”
    A Record of weather events in Minnesota and Wisconsin going back a ways.
    Has some good examples of catastrophic events way back when CO2 was under 350.

    http://www.crh.noaa.gov/Image/arx/research/Cli19DayInHistory.pdf

    Reply
  6. D. Self says:
    May 11, 2014 at 1:31 am

    We can only wish these morons would disappear.

    Reply
  7. Joe says:
    May 11, 2014 at 4:35 am

    In the end, the NCDC will all just melt away.

    Reply
  8. Perry says:
    May 11, 2014 at 7:05 am

    In the end, the NCDC will all just f f f f fade away.

    Reply
  9. _Jim says:
    May 11, 2014 at 1:41 pm

    And … today, Sunday, still down …

    From: http://www.isitdownrightnow.com/ncdc.noaa.gov.html

    Results:

    . . . Ncdc.noaa.gov Server Status Check

    Website Name: . . . National Climatic Data Center
    URL Checked: . . . http://www.ncdc.noaa.gov
    Response Time: . no response
    Down For: . . . . . ~1 day 15 hours

    .

    Reply
  10. _Jim says:
    May 11, 2014 at 2:01 pm

    Meanwhile http://www.interworld.net/cgi-bin/nph-traceroute.cgi reports the tracert results as:

    – – – – – – – – – – – –

    Traceroute http://www.ncdc.noaa.gov

    Starting TRACEROUTE now…
    traceroute: Warning: http://www.ncdc.noaa.gov has multiple addresses; using 205.167.25.172
    traceroute to ncdc.noaa.gov (205.167.25.172), 64 hops max, 52 byte packets
    1 1wil-router (206.124.227.1) 0.256 ms 0.195 ms 0.171 ms
    2 216-243-117-253.abq.static.fttx.citylinkfiber.net (216.243.117.253) 124.846 ms 2.344 ms 1.155 ms
    3 ae7-657.edge6.LosAngeles1.Level3.net (4.31.48.213) 0.549 ms 0.361 ms 0.408 ms
    4 vlan60.csw1.LosAngeles1.Level3.net (4.69.144.62) 64.483 ms
    vlan80.csw3.LosAngeles1.Level3.net (4.69.144.190) 64.590 ms
    vlan60.csw1.LosAngeles1.Level3.net (4.69.144.62) 64.415 ms
    5 ae-83-83.ebr3.LosAngeles1.Level3.net (4.69.137.41) 62.201 ms 62.174 ms
    ae-73-73.ebr3.LosAngeles1.Level3.net (4.69.137.37) 62.117 ms
    6 ae-12-12.ebr1.Washington1.Level3.net (4.69.132.82) 62.736 ms 63.739 ms 63.707 ms
    7 ae-91-91.csw4.Washington1.Level3.net (4.69.134.142) 62.745 ms
    ae-61-61.csw1.Washington1.Level3.net (4.69.134.130) 64.393 ms
    ae-71-71.csw2.Washington1.Level3.net (4.69.134.134) 64.379 ms
    8 ae-2-70.edge6.Washington1.Level3.net (4.69.149.73) 64.634 ms
    ae-3-80.edge6.Washington1.Level3.net (4.69.149.137) 62.566 ms
    ae-2-70.edge6.Washington1.Level3.net (4.69.149.73) 63.694 ms
    9 GOV0084.edge6.Washington1.Level3.net (4.79.198.10) 64.654 ms 64.536 ms 64.480 ms
    10 140.90.111.46 (140.90.111.46) 65.494 ms 64.491 ms 65.317 ms
    11 140.208.63.29 (140.208.63.29) 63.574 ms 63.499 ms 63.500 ms
    12 * * *
    13 205.167.25.226 (205.167.25.226) 79.850 ms 78.858 ms 79.763 ms
    14 205.167.25.225 (205.167.25.225) 78.194 ms 95.866 ms 77.946 ms
    15 205.167.25.234 (205.167.25.234) 79.221 ms 80.415 ms 80.238 ms
    16 * * *
    17 * * *
    18 * * *
    19 * * *
    20 * * *
    21 * * *
    22 * * *

    – – – – – – – – – –

    Interesting to see this message coming back:

    ” Warning: http://www.ncdc.noaa.gov has multiple addresses; “

    Reply
  11. _Jim says:
    May 11, 2014 at 2:14 pm

    Success using an alternative address:

    . . . . . http://205.167.25.171/

    The additional address was found using these people:

    http://mxtoolbox.com/SuperTool.aspx?action=a%3ancdc.noaa.gov&run=toolpage

    and entering “ncdc.noaa.gov” in the “DNS lookup” box.

    This is what comes back:

    Type . . Domain Name . . .IP Address . . . . . . TTL
    A . . . . . ncdc.noaa.gov . 205.167.25.171 . . . 60 min
    A . . . . . ncdc.noaa.gov . 205.167.25.172 . . . 60 min

    – – – – – – – – – – –

    Reply
  12. _Jim says:
    May 11, 2014 at 2:24 pm

    And this works as well:

    . . . . . http://205.167.25.172/

    But, accesses via http://www.ncdc.noaa.gov/ still do not still work (for me), and I am using “8.8.8.8” as my DNS server address (which is Google) per: https://developers.google.com/speed/public-dns/

    So, it looks like there may be DNS name resolution problem that has cropped-up somewhere in resolving ncdc name to the actual IP address.

    .

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *