Most of the sites served by Akamai seem to be wacky this afternoon from Chicago.
Probably the March Madness stuff, but its really bad today - Chicagotribune.com wont load at all
from here and SunTimes.com is missing all of its images.
Are others seeing this problem from other locations? Getting alot of support calls from folks....
Hi there..
Chicagotribune.com is coming up from here (Toronto area) but very slow
loading.... suntimes.com loads nice and fast from here.
Having said that, we're an Akamai powered network here so presume
most/all is coming from local caches.... didn't break down each page to
see sources...
Paul
Its something to do with Akamai in Chicago. Been flakey all day.
Belive it or not, noc@akamai.com is a real address which is read and responds 24/7.
Perhaps using the RFC required address would be more productive than e-mailing 10k strangers?
Patrick Gilmore wrote [context inserted]:
Perhaps using the RFC required address [noc@akamai] would be more
productive than e-mailing 10k strangers?
Normally I see emails like this and, if it's Not In My Back Yard, and the
Internet is not going nutz, the delete key explains how worried i am.
Back to your email:
using the RFC required address
The correct catty response to the Akamai question is : ccare@akamai.com.
That's C as in "Customer", Care as in "they actually care".
I would end the email there, but it really gets me how someone that is
in-house doesn't realize that noc@akamai is a black hole.
Drive Slow,
-paul
Paul Wall wrote:
Patrick Gilmore wrote [context inserted]:
Perhaps using the RFC required address [noc@akamai] would be more
productive than e-mailing 10k strangers?
Normally I see emails like this and, if it's Not In My Back Yard, and the
Internet is not going nutz, the delete key explains how worried i am.Back to your email:
using the RFC required address
The correct catty response to the Akamai question is : ccare@akamai.com.
That's C as in "Customer", Care as in "they actually care".I would end the email there, but it really gets me how someone that is
in-house doesn't realize that noc@akamai is a black hole.
Paul, you might want to test a theory of this nature before you post about it to more than a thousand of your colleagues. This morning I sent email to noc@akamai.com and received a personalized (non-autoresponder) reply 17 minutes later.
jc
Not to add to a potential "peeing" contest here.... but we have Akamai
equipment in our network - it's a very important component to our
service delivery. If/when there is ever a problem (quite rare in our
experience other than the odd hardware failure that has no impact
anyways due to the cluster configuration) we send an email to
noc@akamai.com.
Typical response times on a 24X7 basis never normally exceed 20 minutes
at most. I can remember one time where it might have been an hour.
That's a long ways from "blackhole" based on our experience...
Paul Stewart
I usually just call their toll free support number when their are occasional issues. This is from a content provider perspective (using Akamai as a CDN for the sites I support). Never had an issue getting a hold of anyone and getting the issue resolved (two times I have called them, it was issues on our side anyway).
Paul Stewart wrote:
I am pleased hear that Akamai has remedied this situation, most likely
by having Mr. Gilmore attend to the matter personally.
Drive Slow,
Paul Wall
Paul Wall wrote:
Nothing is unfounded. I've previously had issues reaching Akamai at
noc@akamai.com, which is why I suggested that the poster try the
ccare@ address.
It was subsequently demonstrated (by Patrick and others) that the noc@
account is currently monitored satisfactorily.
Any further discussion would be off-topic, so I'll bow out now. Drive Slow.
Paul Wall
[Akamai customer. Hi.]
Akamai customer support is ccare@. It's in all the literature, and their
support site. You're arguing a suboptimal answer.
Customers with issues should use Akamai Edgecontrol. This is from the
horse's mouth[1]. They can also use, and anyone can use, the ccare@ box.
The ccare@ email address interfaces to Edgecontrol and tons of other Akamai
sorcery[2], which does a whole bunch of jedi nunchuckery[3], giving the ops
tech a lot more info out of the gate.
Anyone claiming noc@ : not the place for issues to go to, and Akamai will
tell you that.[4]
Moving on, nation :
What bugs me about this thread(thanks for asking!) is that someone posted to
the list, trying to troubleshoot a problem affecting multiple customers. He
tried (brace yourself) collaboration, and was met with a quasi shot across
the bow from someone At That Company. If you want to judge (how do I
configure my router for that?), I'd point to the key employee of said
vendor, who, instead of replying to the poster with a ticket number and
ownership, "posted to 10k strangers" a snarky comment that one shouldnt post
"to 10k strangers". Orly.
Now, I have nothing against anyone in this situation - we all get testy..
arguably, I am now 
Not looking to start a flame war. E-mail who you
want.
Obligatory Win : Someone wrote in this thread earlier re emailing noc@ and
getting an email back in 17 minutes. For what it's worth, I forwarded the
original two posts to *ccare@* (before the war) (with no other contact info,
specifically stating it was someone else's problem) and got a phone call in
less than five.
Whut whut? If only /all/ vendors' systems were that good..
-j.
[1] www.akamai.com/html/support/
[2] www.akamai.com/html/technology/
[3] i believe that is the technical term they used, yes.
[4] +1 877 4 akatec.
jamie rishaw wrote:
Akamai customer support is ccare@.
<snip>
Anyone claiming noc@ : not the place for issues to go to, and Akamai will
tell you that.[4]
No one said that noc@ was "not the place" - someone (who works at Akamai) said that the RFC specified noc@ works, and it does. Someone else said it didn't work, and that person was incorrect (as my testing proves) - perhaps the NOC has better things to do than engage with a nym/troll when it "tests" if the noc@ address works or not.
To summarize:
The RFC-specified noc@ address exists and works. Customers also have/know about ccare@ which also works. Non-customers (surprise - not everyone is an Akamai customer, and non-customers do have valid reasons to contact a NOC now and then) who don't know about the super sekret[1] ccare@ can use noc@.
Is there some point you wanted to make that contradicts all of this?
jc
[1] TIN(Sekret)C