Hello everyone,

There will be extended downtime on Thursday, 25 January for work on the EVE Online Network and Hardware.

We expect this work will take up to 10 minutes beyond the regular downtime end time and estimate that the server will be available at 11:25 UTC.

Please note that TQ will be bought back online as soon as the work is completed, which can be ahead of schedule of the previously mentioned downtime.

Updates of the progress will be posted here, and if the update time exceeds this window, it will also be posted on the status page.

Edit:
Work was completed ahead of schedule and Tranquility was online and accepting connections at 11:13 UTC

Added to the known issues above. We’re aware of it and looking to rectify it.

Thanks for the feedback everyone. This should once again be working correctly!

Hey Everyone!

During today’s downtime, we issued the entire reward track to all those who had reached the first milestone of 50 points during the Crimson Harvest. These have been added directly to the character.

Thank you all for your patience!

(Updating the original message and marking as resolved)

Greetings Excel-ing Capsuleers,

The Monthly Economic Report for October is ready for your review.

You can find the downloadable data for last month’s report in the following LINK .

o7

Hey everyone,

Just as an update from CCP Swift’s message above (I’ll also add this to his post):

The root cause of the issue that occurred over the weekend has been identified. Unfortunately, however, the event has concluded as of downtime today. Whilst we understand this can be incredibly frustrating to those of you who were intending to progress in that final weekend, we have instead decided to award any character who reached the first milestone, of 50 points, to be supplied the entire reward track of SKINS directly added to their character.

We are in the process of investigating the best method to get these delivered and once a timeline has been established we will relay that here as well.

If you have sufficient space and you’ve tried the “Fix permissions” option from the folder and it’s still unresolved, it might be worth trying the new launcher - Download the free EVE Online client (launcher) for Windows or Mac to see if you have any success.

Try a relogin - remove your account and re-add them?

Hello everyone,

There will be an extended downtime on Wednesday, 1 November for work on the EVE Online launcher support. (We will be working on activating the EVE SSO JWT Token again.)

We expect this work to take up to an additional 5 minutes beyond the regular downtime end time, and estimate that the server will be available at 11:20 UTC.

PLEASE NOTE that TQ will be brought back online as soon as the work is completed which can be ahead of schedule of the previously mentioned downtime.

Updates of the progress will be posted here and if the update time exceeds this window it will also be posted on the EVE Status Twitter and Status page.

11:00 UTC: Update started.
11:07 UTC: Update complete
11:08 UTC: Resetting and testing affected systems
11:13 UTC: Finishing up, we should be ready to Tranquility into VIP mode shortly.
11:14 UTC: Starting up in VIP now.
11:15 UTC: Boot successful, TQ is now in VIP, performing final tests.
11:23 UTC: VIP Disabled. Tranquility is live!

Edit: If you ar...

Hey everyone,

This was once again implemented during downtime on 31 October but rolled back.

This is going to be attempted during an extended downtime on Wednesday 1 November.

The initial post will be updated to reflect this change.

Not sure why you’re seeing this as updates are appearing on there?

image604×757 49.4 KB

We can certainly investigate once this current issue is over but for now, I’d recommend referring to the status page for updates!

Hey everyone,

We’re aware of issues with Chat and login.eveonline.com currently and are under investigation.

Any updates will be posted here and on the EVE Status Twitter and Status page.

11:20 UTC - Server opened following extended downtime
11:25 UTC - Issues with chat reported and under investigation
12:08 UTC - Several services have been identified as having issues and we are working on resetting them back to a known working state.
12:14 UTC - SSO Issues should now be resolved. Additional services are still being worked on.

CCP Arcade taking over messaging.

12:39 UTC - If you continue to see issues such as with chat channels then please try restarting your EVE client and logging back in.

13:03 UTC - In-game issues should be resolved with a restart of the EVE client. We’re aware of issues with a recent update to the Beta launcher.

A launcher update was deployed at around 12:03 - Issues with the launcher are likely unrelated to the issues that arose after downtime. If you are encou...

A separate thread has been set up following today’s extended downtime issues over here: Chat Issues and login.eveonline.com Issues - 31st October 2023

I’m going to lock this thread for now so we keep the ongoing issues in one location.

Hello everyone,

There is a small chance of extended downtime again on Tuesday, 31 October. Following yesterday’s network update we are going to switch over the EVE SSO JWT Token today.

We expect to be able to complete this within the regular downtime window 11:00 UTC - 11:15 UTC, but this process may take up to an additional 5 minutes.

PLEASE NOTE that TQ will be brought back online as soon as the work is completed which can be ahead of schedule of the previously mentioned downtime.

Updates of the progress will be posted here and if the update time exceeds this window it will also be posted on the EVE Status Twitter and Status page.

11:01 UTC - Update started
11:13 UTC - Update deployed
11:15 UTC - The update has been reverted again
11:17 UTC - TQ starting in VIP
11:18 UTC - TQ Online in VIP
11:20 UTC - Testing on TQ ongoing
11:21 UTC - Resetting the SSO
11:25 UTC - VIP Removed

We’re aware of other issues extending beyond this post - a separate thread will be created now, but please ...

Tranquility online as of 11:14:01 UTC!

Marking as complete - thank you for your patience.

Morning everyone.

This has been postponed one more day to the 31st of October, to allow for network upgrades scheduled for today to go as smoothly as possible.

I’ll once again update the thread tomorrow following the switchover.

I just updated the change log and post title - this will be re-run again during downtime on Monday 30 October.

There is also a network upgrade scheduled for the same time - a separate thread has been set up to track potential downtime as well. Any unexpected downtime messaging will be relayed there.

Upon conclusion of the update, I’ll relay any related messages to this thread.

Hello everyone,

There is a small chance of extended downtime on Monday, 30 October while we conduct network upgrades at downtime.

We expect to be able to complete this within the regular downtime window, but this process may take additional time.

PLEASE NOTE that TQ will be brought back online as soon as the work is completed which can be ahead of schedule of the previously mentioned downtime.

Any updates will be posted here and on the EVE Status Twitter and Status page.

Edit : 11:01 UTC- Update is in progress, estimated time of completion is 11:20
Edit: 11:13 UTC - Update complete. TQ is booting.
Edit: 11:14 UTC - Tranquility is online and accepting connections

Its mentioned in the top post - if you’re having problems logging in, completely remove your account and re-add it, it should resolve the issue for you if you’re getting this alert.

Greetings 3rd party developers!

Just wanted to give notice of an update heading your way during downtime:

Tokens will now include the URL schema in the ‘iss’ (issuer) claim, aligning more closely with relevant specifications.

As an example, effectively the iss claim of the JWT token will change from login.eveonline.com to https://login.eveonline.com

This has been a part of the existing esi documentation here as point 2: Validating JWT tokens from the EVE SSO | esi-docs so it should be included in the workflow of your app already, otherwise, it may need some adjustment to accommodate this.

Apologies for the late notice of this update, we just wanted to ensure it was communicated prior to the change.

Edit:
11:25 UTC - 19th October: This change was implemented at 11:00 UTC, however, it has been temporarily reverted to resolve additional underlying issues. This deployment has been postponed for now. I’ll update this post once a new date/time is established.

17:00 UTC - 27th October: This i...