.mac mail down?

Posted:
in Mac Software edited January 2014
Can´t connect via Mail, webmail OR iloveapple.com (which have always been my last resort).



And now <a href="http://www.mac.com"; target="_blank">www.mac.com</a> doesn´t work either.



And Apple support pages don´t work either.



Whats up? I really need my mail right now. Am I the only one?

Comments

  • Reply 1 of 11
    applenutapplenut Posts: 5,768member
    doesnt work here either
  • Reply 2 of 11
    eugeneeugene Posts: 8,254member
    An exploit of MS SQL resulted in a denial of service attack on many domains yesterday.
  • Reply 3 of 11
    [quote]Originally posted by Eugene:

    <strong>An exploit of MS SQL resulted in a denial of service attack on many domains yesterday.</strong><hr></blockquote>



    this is interesting. does that mean that MS SQLserver is used by mac.com or would this just reflect that the DNS root servers do? perhaps the datacentre that hosts .mac are responsible?



    some sites are still down (macosrumors.com for example)
  • Reply 4 of 11
    torifiletorifile Posts: 4,024member
    As I understand it, the problem isn't that the sites are down, it's that the internet is just slow. My site is 'down' as well, but I KNOW that there is nothing MS related on that machine. Apache/PHP/MySQL running 10.2. CNet had an article <a href="http://news.com.com/2100-1001-982131.html?tag=fd_top"; target="_blank">here</a>.
  • Reply 5 of 11
    [quote]Originally posted by torifile:

    <strong>As I understand it, the problem isn't that the sites are down, it's that the internet is just slow. My site is 'down' as well, but I KNOW that there is nothing MS related on that machine. Apache/PHP/MySQL running 10.2. CNet had an article <a href="http://news.com.com/2100-1001-982131.html?tag=fd_top"; target="_blank">here</a>.</strong><hr></blockquote>



    strange then how some sites stay affected whilst others (such as this one) remain their same speedy selves.



    sorry to here about your site. earlier today, my site was also affected but things seemed to have sorted themselves out now. would this be certain backbones still being buckled by the worms payload?
  • Reply 6 of 11
    torifiletorifile Posts: 4,024member
    [quote]Originally posted by lungaretta:

    <strong>



    strange then how some sites stay affected whilst others (such as this one) remain their same speedy selves.



    sorry to here about your site. earlier today, my site was also affected but things seemed to have sorted themselves out now. would this be certain backbones still being buckled by the worms payload?</strong><hr></blockquote>



    My site's fine now. I don't think that the site itself was affected, just the route to it was screwed up. Like you said, the backbones were suffering and not individual sites. Stupid MS. I do all I can to make sure my computer is security problem free and MS still manages to screw it up. They are a menace to society.
  • Reply 7 of 11
  • Reply 8 of 11
    [quote]Originally posted by torifile:

    <strong>

    They are a menace to society.</strong><hr></blockquote>



    i'd leave it as just: they are a menace



    seconds after my last post, my site is down again. seems to be another stupid m$sqlserver user in the vicinity of my site <img src="graemlins/oyvey.gif" border="0" alt="[oyvey]" />



    i guess all i can do now is wait for the worm to finish looking for new hosts...
  • Reply 9 of 11
    eugeneeugene Posts: 8,254member
    The Gates e-mail and the unleashing of this worm is probably not a coincidence. Somebody's been sitting on this worm for a few months waiting for an opportunity to slap MS in the face. That opportunity came. The hole itself was patched 6 months ago, but you know how stupid administrators are...



    As for why .Mac was down. .Mac and Apple Store servers aren't part of the Akamai network, though some images and other objects on their pages might be. Those servers became islands, cut off from the rest of the net because all possible routes were congested, detours and all. Imagine any big city during rush-hour. You don't get anywhere because of the sheer volume of traffic. That doesn't include the root nameservers, which associate IPs with domains. So, along with gridlock, there was a lot of traffic out there travelling blind...



    Some sites seemed unaffected because they probably weren't too many hops away. Akamai relays are a good example. You don't have to get on the major backbones and arteries to get to every server...
  • Reply 10 of 11
    [quote]Originally posted by Eugene:

    <strong> Imagine any big city during rush-hour. You don't get anywhere because of the sheer volume of traffic. That doesn't include the root nameservers, which associate IPs with domains. So, along with gridlock, there was a lot of traffic out there travelling blind....</strong><hr></blockquote>



    good analogy
  • Reply 11 of 11
    torifiletorifile Posts: 4,024member
    It wasn't just the DNS root servers that were affected. I was unable to reach my server even after typing in my IP address. I think you're right, Eugene, that the timing was not accidental. Some planned this one good.
Sign In or Register to comment.