We just had a small earthquake here in Southern California. The end is near!
Ha ditto! Not far from Riverside. Felt it in Upland.
EDIT: 1.8 centered in Devore. No biggy.
We just had a small earthquake here in Southern California. The end is near!
Ironic, just had a small earthquake too. What a night.
In other news, I can finally re-authenticate all my apps that got screwed up thanks to the certificates. Tweetbot, here I come!
We just had a small earthquake here in Southern California. The end is near, but at least all of my Apple online services are working again.![]()
Ah I see it now - 3.4 - yehaw. http://scedc.caltech.edu/recent/Maps/117-34.html
Btw - Issue still remains here. Can't get anything above 56K downloads in App Store, even though I'm on 200Mbps connection.
Everything for me is now normal. MidWestBtw - Issue still remains here. Can't get anything above 56K downloads in App Store, even though I'm on 200Mbps connection.
Lucky! We have Charter here. 60/4 is all I get.
Everything for me is now normal. MidWest
Sounds like you might need a technician to come to your residence to check stuff out.Btw - Issue still remains here. Can't get anything above 56K downloads in App Store, even though I'm on 200Mbps connection.
Sounds like you might need a technician to come to your residence to check stuff out.
Only thing that I can stand TWC for is internet. TV is horrible, but internet always delivers. We are on a 200/20 connection.
I have heard mixed things about TWC, but at least Charter has been pretty reliable for me. All I have is their internet. I wish FiOS would hurry up. Literally, businesses about half a mile north of my house got FiOS, but we got left out.
If it's widespread, why are all of us ok???? It's more likely you are having hardware/local network issuesIts not a TWC issue. Again, Apple has verified the issue on their own servers. They are unable to ping their own server. Additionally, I have tested 6 different WiFi networks. (School, work, friends, Starbucks). None can ping the server. Its a much bigger issue that a single person experiencing it. If Apple cannot ping their own server, it must be major.
Thats all I am trying to get at. Its bigger than just me.
OUCH
Apple has updated its system status page to reflect widespread issues affecting multiple Apple products and services since approximately 7:30 PM Pacific, including the App Store, Apple TV, iBooks Store, iTunes Match, iTunes Store, Mac App Store and Radio.
![]()
Many users are also unable to fully access or use the Apple website, Apple Online Store, Apple ID, Apple Music, FaceTime, iCloud, iMessage, Mail, TestFlight and several other Apple services, suggesting possible larger server or DNS issues.
Apple's standard response on its system status page says it is investigating and will provide a status update as more information becomes available.
Update 8:38 PM: Apple's system status page now indicates the issues have been resolved, and users are indeed reporting Apple's services are up and running once again.
Article Link: Multiple Apple Services Experiencing Widespread Outage [Updated]
If it's widespread, why are all of us ok???? It's more likely you are having hardware/local network issues
I tried pinging gs.apple.com too and it also times out for me (in NYC area, on Comcast); however, I *can* open a webpage in Safari at gs.apple.com from the same device at the same time the pings are failing. It could simply be that Apple has turned off ICMP echo (aka ping) on/for that server(/cluster/firewall/etc.)... just a thought....Its not a TWC issue. Again, Apple has verified the issue on their own servers. They are unable to ping their own server. Additionally, I have tested 6 different WiFi networks. (School, work, friends, Starbucks). None can ping the server. Its a much bigger issue that a single person experiencing it. If Apple cannot ping their own server, it must be major.
Thats all I am trying to get at. Its bigger than just me.
On WiFi or just cellular? The big issue is WiFi related.
I tried pinging gs.apple.com too and it also times out for me (in NYC area, on Comcast); however, I *can* open a webpage in Safari at gs.apple.com from the same device at the same time the pings are failing. It could simply be that Apple has turned off ICMP echo (aka ping) on/for that server(/cluster/firewall/etc.)... just a thought....
Not to bicker with Tier2@Apple, but a lot of Apple's servers don't reply to pings. I suggest the next time you deal with them ask them to supply you with an IP address (rather than a DNS name, which you already have, or a new DNS resolver) for the server and try to ping that IP directly. The primary reason I suggest this is that in the ping sample you gave above, gs.apple.com resolves to gs.apple.com.akadns.net. - which indicates the Akamai CDN, which would make it NOT Apple's server.I can also access it via safari and so can the apple engineers. But they are unable to ping just like we can't. They said that's not suppose to happen. Meaning we should be able to ping. I changed the DNS settings on my router and I could ping the server but only 1/5 went through before it timed out. So it's definitely a work in progress on their end. They supplied me with DNS settings that they use on campus.
Apple has updated its system status page to reflect widespread issues affecting multiple Apple products and services since approximately 7:30 PM Pacific, including the App Store, Apple TV, iBooks Store, iTunes Match, iTunes Store, Mac App Store and Radio.
![]()
Many users are also unable to fully access or use the Apple website, Apple Online Store, Apple ID, Apple Music, FaceTime, iCloud, iMessage, Mail, TestFlight and several other Apple services, suggesting possible larger server or DNS issues.
Apple's standard response on its system status page says it is investigating and will provide a status update as more information becomes available.
Update 8:38 PM: Apple's system status page now indicates the issues have been resolved, and users are indeed reporting Apple's services are up and running once again.
Article Link: Multiple Apple Services Experiencing Widespread Outage [Updated]