# Lots of "Received status code 429 for tile content" errors

**URL:** <https://community.cesium.com/t/lots-of-received-status-code-429-for-tile-content-errors/28851>\
**Category:** Cesium for Unreal\
**Created:** [December 21, 2023, 3:28am UTC](https://community.cesium.com/t/lots-of-received-status-code-429-for-tile-content-errors/28851 "2023-12-21T03:28:21Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![aidnewsome](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/aidnewsome/32/12077_2.png) [@aidnewsome](https://community.cesium.com/u/aidnewsome)\
**Post date:** [December 21, 2023, 3:28am UTC](https://community.cesium.com/t/lots-of-received-status-code-429-for-tile-content-errors/28851/1 "2023-12-21T03:28:21Z")

</div>

Hi,

What’s going on here? My project in the Editor suddenly has all these errors and isn’t displaying correctly. The Packaged Project doesn’t have these issues at the moment. I’m confused…

 ![Cesium_Bug](https://global.discourse-cdn.com/cesium/original/3X/3/b/3b1795387575bf77e8730cc6d4150b87b5d4b4b5.jpeg)  
 ![Cesium_Errors](https://global.discourse-cdn.com/cesium/original/3X/d/f/df90cf7ebdf985adba316afc1713f17b5b6fc0a1.png)

Thanks,

Aidan

---

<div class="post-metadata">

**Author:** ![czoog](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/czoog/32/14000_2.png) [@czoog](https://community.cesium.com/u/czoog)\
**Post date:** [December 21, 2023, 3:43am UTC](https://community.cesium.com/t/lots-of-received-status-code-429-for-tile-content-errors/28851/2 "2023-12-21T03:43:55Z")

</div>

Having the same issue. Started sometime tonight. I checked google maps api status page and it all looks ok. Not sure what is happening. Hopefully fixed soon ☹

---

<div class="post-metadata">

**Author:** ![aidnewsome](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/aidnewsome/32/12077_2.png) [@aidnewsome](https://community.cesium.com/u/aidnewsome)\
**Post date:** [December 21, 2023, 4:00am UTC](https://community.cesium.com/t/lots-of-received-status-code-429-for-tile-content-errors/28851/3 "2023-12-21T04:00:29Z")

</div>

I’ve been trying to troubleshoot and no luck. I’m glad to hear I’m not the only one…

---

<div class="post-metadata">

**Author:** ![aidnewsome](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/aidnewsome/32/12077_2.png) [@aidnewsome](https://community.cesium.com/u/aidnewsome)\
**Post date:** [December 21, 2023, 4:01am UTC](https://community.cesium.com/t/lots-of-received-status-code-429-for-tile-content-errors/28851/4 "2023-12-21T04:01:56Z")

</div>

I also tried creating another temporary Cesium account and using that as my credentials. It didn’t work either.

---

<div class="post-metadata">

**Author:** ![czoog](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/czoog/32/14000_2.png) [@czoog](https://community.cesium.com/u/czoog)\
**Post date:** [December 21, 2023, 4:03am UTC](https://community.cesium.com/t/lots-of-received-status-code-429-for-tile-content-errors/28851/5 "2023-12-21T04:03:48Z")

</div>

429 is a quota error as in quota exceeded, but looking at my usage I am not even close to the 1000/month intro quota cesium gives us. There could be a daily quota, though, not sure.

---

<div class="post-metadata">

**Author:** ![aidnewsome](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/aidnewsome/32/12077_2.png) [@aidnewsome](https://community.cesium.com/u/aidnewsome)\
**Post date:** [December 21, 2023, 4:04am UTC](https://community.cesium.com/t/lots-of-received-status-code-429-for-tile-content-errors/28851/6 "2023-12-21T04:04:34Z")

</div>

I read that there isn’t anymore but that’s why I’m confused. I’ve been using it a lot today, but I’ve never had that issue before. Ugh, I need help bad!

---

<div class="post-metadata">

**Author:** ![aidnewsome](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/aidnewsome/32/12077_2.png) [@aidnewsome](https://community.cesium.com/u/aidnewsome)\
**Post date:** [December 21, 2023, 4:07am UTC](https://community.cesium.com/t/lots-of-received-status-code-429-for-tile-content-errors/28851/7 "2023-12-21T04:07:28Z")

</div>

Are you having the same problem for sure? I just tried in a blank project with a fresh account and it didn’t work either.

---

<div class="post-metadata">

**Author:** ![aidnewsome](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/aidnewsome/32/12077_2.png) [@aidnewsome](https://community.cesium.com/u/aidnewsome)\
**Post date:** [December 21, 2023, 4:18am UTC](https://community.cesium.com/t/lots-of-received-status-code-429-for-tile-content-errors/28851/8 "2023-12-21T04:18:00Z")

</div>

I do have a major spike in usage today. Could this be why?

 ![Spike](https://global.discourse-cdn.com/cesium/original/3X/4/e/4eb3ab3115e87682cedc0c6f9ba643fd58825a07.png)

---

<div class="post-metadata">

**Author:** ![czoog](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/czoog/32/14000_2.png) [@czoog](https://community.cesium.com/u/czoog)\
**Post date:** [December 21, 2023, 4:49am UTC](https://community.cesium.com/t/lots-of-received-status-code-429-for-tile-content-errors/28851/9 "2023-12-21T04:49:29Z")

</div>

I think it’s an issue with cesium’s api key from google. I switched to my own google maps api key and it works fine.

---

<div class="post-metadata">

**Author:** ![Kevin\_Ring](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/kevin_ring/32/2003_2.png) [@Kevin\_Ring](https://community.cesium.com/u/Kevin_Ring)\
**Post date:** [December 21, 2023, 4:51am UTC](https://community.cesium.com/t/lots-of-received-status-code-429-for-tile-content-errors/28851/10 "2023-12-21T04:51:43Z")

</div>

Yes you’re right, the Google account used by Cesium ion has hit its quota limit. We’ll get this sorted as soon as we can, but in the meantime the only workaround is to use your own API key obtained via Google Cloud, rather than accessing Google Photorealistic 3D Tiles via Cesium ion. Sorry for the hassle!

Daily quotas reset at midnight Pacific Time so it should start working again in about 3 hours.
