Looks like it's partially back up, although it seems work is still ongoing, as I am getting slow load times and 504 Gateway Time-out errors
Hopefully it's fully back up soon
Until then, you will probably still see errors logging into the game, and accessing the website or API, so just give it some more time
Seems like they are moving servers to a new datacentre (it's now being hosted in AWS) which is a much more involved operation than standard maintenance.
Good news is that from earlier today, we can see it was at least running briefly, so I'd guess the bulk of the migration is done, at this point it's probably more a matter of fixing any issues and getting it fully up to expected performance (again, just guessing, I don't know the specifics).
Could still be a bit longer though - even though it's not a change visible to players, this kind of operation has a lot going on behind the scenes.
a month ago
@EA_CadeSince this maintenance was done, the https version of the site is broken: all static assets (creature pngs etc) won't load. This is especially noticeable for me in Firefox, with the "HTTPS-Only Mode" setting enabled, which upgrades requests to use https instead of http. The result is that all creation cards show up blank instead of the image (see screenshot).
This is caused by every request to https://static.spore.com returning a 503 error - but only when using https.
Not sure if this is already known to the team, so I thought I'd let you know as it is a non-default browser setting.
a month ago
I'm noticing the issue on static.spore.com when using HTTPS as well, however, it does not seem to affect all creations. A small number are fine.
For example, the current most recent featured creation works fine: https://static.spore.com/static/thumb/501/099/886/501099886802.png
But the second-most recent featured creation does not: https://static.spore.com/static/thumb/501/099/876/501099876776.png
The former works fine on both http and https, while the latter works fine on http but gives 503 "An error occurred while processing your request." on https.
Thinking it might be some caching/CDN issue. I've disabled browser cache (via devtools) to rule that out. Screenshot of devtools is attached.