1903597 - (akamai-blocks) Sites blocked by Akamai

Status: NEW

(Web Compatibility :: Knowledge Base, defect, P3)

Description

[James Graham [:jgraham]]

Sites are intermittently blocked by Akamai CDN. This seems to be something related to broken bot detection.

Typical symptoms are sites with an Akamai CDN experiencing intermittent failures to load, maybe more often on Linux.

Comment 1

[Dennis Schubert [:denschub]]

A good indication for that is that users get a 403 error page showing a "Reference" number that starts with 18, like 18.46656b8.1718803641.188f49c0.

Comment 2

[Jeff Muizelaar [:jrmuizel]]

There is an Akamai incident being coordinated here: https://mozilla.enterprise.slack.com/archives/C07CLQWJ0N6

Comment 3

[stordlord]

[Tracking Requested - why for this release]:

Release Note Request (optional, but appreciated)
[Why is this notable]:
[Affects Firefox for Android]:
[Suggested wording]:
[Links (documentation, blog post, etc)]:

Comment 4

[Pascal Chevrel:pascalc]

Please don't play with the fields and follow the Bugzilla etiquette, thanks.
https://bugzilla.mozilla.org/page.cgi?id=etiquette.html

Comment 5

[Jeff Muizelaar [:jrmuizel]]

This is mostly happening on Nightly. If anyone sees it on release please send the reference IDs to me and I can send them on to Akamai

Comment 6

[Matt McCutchen]

I'm a user who frequently runs into Akamai blocks with Firefox on Linux (and sometimes also with Firefox on Android or Chromium on Linux), and I just found this bug report. I'm currently using Fedora's firefox-143.0-1.fc42.x86_64. I was trying to shop for some shoes today and got blocked on several different sites. I retested in a new Firefox profile and got the following reference IDs:

kohls.com: 18.1c10de17.1758854470.21bee527
famousfootwear.com: 18.b1813217.1758854507.d61fb3fb
newbalance.com: 0.d80c0317.1758854130.6e450605 (unsure if this one is related because it doesn't begin with 18)

I hope this helps. I would be very happy to see the problem fixed, so let me know if I can help with any other testing. Or let me know if you don't want end users posting their information here.

Comment 7

[Jeff Muizelaar [:jrmuizel]]

Thanks, I've forwarded those id's on to Akamai. We'll see what they say.

Comment 8

[sphakka]

Coming from #1907509... I use FireFox 144.0 (Chromium is also affected) on Gentoo Linux. Further info:

https://community.akamai.com/customers/s/article/Why-is-Akamai-blocking-me?language=en_US.

Could you also please forward this one?

ups.com: 18.5f161502.1762268682.58789c72

I'd like to do it by myself but these stupid mega business trolls are basically impossible to get in touch with unless through a lawyer.

Another option is to contact your ISP, as the issue might also come from some wide-range blacklisting of their network.

Comment 9

[Jeff Muizelaar [:jrmuizel]]

(In reply to sphakka from comment #8)

Coming from #1907509... I use FireFox 144.0 (Chromium is also affected) on Gentoo Linux. Further info:

https://community.akamai.com/customers/s/article/Why-is-Akamai-blocking-me?language=en_US.

Could you also please forward this one?

ups.com: 18.5f161502.1762268682.58789c72

If it's happening in Chrome and Firefox than the problem is probably not browser related and thus out of scope for our discussions with Akamai. You could try changing your UA to more popular one (Firefox or Chrome on Windows). Otherwise, your only option is really to complain to UPS.

Comment 10

[sphakka]

(In reply to Jeff Muizelaar [:jrmuizel] from comment #9)

If it's happening in Chrome and Firefox than the problem is probably not browser related and thus out of scope for our discussions with Akamai. You could try changing your UA to more popular one (Firefox or Chrome on Windows). Otherwise, your only option is really to complain to UPS.

Thanks. Got some progress with the UA trick indeed!

Comment 11

[sphakka]

(In reply to sphakka from comment #10)

(In reply to Jeff Muizelaar [:jrmuizel] from comment #9)

If it's happening in Chrome and Firefox than the problem is probably not browser related and thus out of scope for our discussions with Akamai. You could try changing your UA to more popular one (Firefox or Chrome on Windows). Otherwise, your only option is really to complain to UPS.

Thanks. Got some progress with the UA trick indeed!

Actually, nope it breaks at login whatever the UA :-( Called UPS: worse useless technical help-desk ever. They have no clue what we're talking about.

Hope this is solved soon.

Comment 12

[Stefan Fleiter (:sfleiter)]

This blocks access to dhl.de package tracking site on Nightly for the most important delivery service in Germany as reported in bug 2010880.
Login works flawlessly in Google Chrome or Firefox 147.0.2