Airtable not loading in Chrome

Also not working in Chrome incognito or Firefox. I can’t sign in at all at this point. 

​@anamonroe Airtable is currently experiencing an outage unrelated to this Chrome issue. We hope to be fully recovered soon, but you can follow along at status.airtable.com for updates!

+1 this issue. 

Have tried clearing cache + turning off extensions but still having major issues with Chrome (some bases not loading/timing out, other bases loading sporadically). Works normally in other browsers. 

Also have a couple of clients now reporting this issue with Chrome specifically. 

I am also having this issue as of February 25! Airtable please help us 😭

Still having this issue as of Feb 26 😥

Hello ,

This is very frustrating . We require now to use a different browser only for airtable. Pleaes provide a timeline as when this will be fixed. thank you

Issue is ongoing for a few of our users. Can’t tell why it’s affecting some and not others.

It’s been a problem for me since the 25th and I’m baffled there isn’t better communication on the status page about it. Yes it’s sporadic, but the access issue happens literally every day and totally interrupts flow. 

Hi all, apologies for the slow communication here. We’ve been investigating this issue a lot internally, but have struggled to make much communicable progress because no internal user is able to reproduce it, and the bug comes before Airtable code fully loads, so we don’t have the usual error metadata that we get for other errors. We currently believe the issue to be a bug within Google Chrome and have reported it to them, but the process of getting a bug investigated and resolved at that level is quite slow.

We have one ask for anyone who’s willing: we are looking for people who have NOT clicked the link below and would be willing to join a 15-30 minute debugging session where the debug data may be shared publicly on a Google Chrome bug report. You can reach out to me at benjamin.muschol@airtable.com if you are willing. While we have debugging metadata from users that has helped us pinpoint where in the browser the bug occurs, that metadata includes the user’s browsing activity during the debug session. While we can filter the recording to just be Airtable traffic, we’re uncomfortable sharing it publicly unless the affected user explicitly opts-in beforehand.

Lastly, for anyone who missed the link amongst the thread, clicking this link while logged in to Airtable will opt you into a mitigation that resolves the issue: https://airtable.com/_preview?code=liveAppUnchunked-e4105f3c6f710546969bf4db1ba711aec73d84f91ef3aa821c788c6b14bea018-1188bce2f719bd86ee55fff8b7b5b6ec748b466770ecd6b7871e3cb0b7bda7ab-302add8c813769a40c6822484dd045f6 There may be some non-trivial delay between clicking this link and resolving the issue, but to the best of our knowledge it has eventually resolved it for everyone affected.

Presumably there is some performance trade-off if you click this link? Would clicking the link affect performance in other browsers?

Presumably there is some performance trade-off if you click this link? Would clicking the link affect performance in other browsers?

Yes, it will make the initial page load slower (it will add ~1-2 seconds). This will go away after the initial load because your browser will save it in the cache, but then it will get added back when we update our code which happens once a day.

It will affect every browser you use.

Thanks. If and when a fix is applied, will this change be removed automatically or will it be a manual process of reverting for those that have clicked the link?

> Thanks. If and when a fix is applied, will this change be removed automatically or will it be a manual process of reverting for those that have clicked the link?

We’ll remove it once we identify a permanent fix

Great, thanks.