Update - We finished the migration, and we're now up and running again! We're now providing access to customers incrementally.

We still expect some degraded performance. Due to the amount of downtime that we accumulated, you may also experience lags in the data as we're now catching up with all the events that happened since we started the migration.

The ETA for solving the performance issues is the end of today (Sept, 17th UTC) and we expect to finish catching up with the delayed data during the weekend. We're carefully monitoring it along with the data consistency. Updates will follow.

Thank you for bearing with us and to the team who are pulling crazy hours to make this a success.

Again, we apologize for the inconvenience and do not expect such large maintenance windows to be the norm.
Sep 17, 18:27 CEST

Update - Scheduled maintenance is still in progress. We will provide updates as necessary.
Sep 17, 17:56 CEST

Update - We're about to finalize the migration, in order to complete it our application will be inaccessible during this period.

The latest ETA for returning back to normality is still Sept, 17th end of the day UTC.

Thank you for bearing with us and to the team who are pulling crazy hours to make this a success.

Again, we apologize for the inconvenience and do not expect such large maintenance windows to be the norm.
Sep 17, 12:04 CEST

Update - We've decided to spin up a fallback instance on back up data and continue the migration in the background.

Thus the product is now functional again. However, the data is frozen since Sept, 14th, date when we did the back up. Newer events won't be part of the insights until we finish the migration successfully.

The latest ETA for the migration is Sept, 17th end of the day UTC.

Again, we apologize for the degraded experience.
Sep 16, 20:00 CEST

Update - Since the migration is having a bigger impact than expected, we have decided to spin up a new instance on back up data. This will allow our users to access the product again in approximately 3h. The migration to new GitHub IDs is still continuing in the background.
Sep 16, 13:14 CEST

Update - Our migration is currently still ongoing, a more extensive update on its progress including an ETA on completion will follow later today. Thank you for bearing with us and to the team who are pulling crazy hours to make this a success.
Sep 16, 06:56 CEST

In progress - Our migration has started, due to the size and scale of the migration and our dependency on Github's migration to their new ID format we expect 24-48 hours of down time.
Sep 14, 16:30 CEST

Update - We are about to start the migration, our application will be inaccessible during this period.

Scheduled - GitHub GraphQL API has recently started migrating to a new global ID format.

More on this here https://github.blog/2021-02-10-new-global-id-format-coming-to-graphql/.

For Athenian to be able to continue to provide up to date insights, our backend needs to undergo a large scale migration to the new ID format.

The downtime of this complex maintenance operation is estimated to 24-48h.

We apologize for the inconvenience and do not expect such large maintainance windows to be the norm.