Skip to content

Incident detail

Customer portal issues

Resolved incidentMinor1 affected service

Timeline window

to

Get alerted the next time Neo4j Aura breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. Identified

    We are currently experiencing some delay in the full data migration to our new customer portal.

    Currently some customers may face issues logging in. When you receive the welcome email you will be able to sign-in.

    Aura customers cannot accept invites to their environments and the fix for this is also currently in progress.

    If you cannot yet access the support portal but need to raise a support issue, please use support@neo4j.com.

  2. Identified

    We are continuing to work on a fix for this issue.

  3. Identified

    We continue to work on the completion of the data migration to restore full access to the customer portal.

    Currently some customers may face issues logging in. When you receive the welcome email you will be able to sign-in.

    Aura customers cannot accept invites to their environments and the fix for this is also currently in progress.

    If you cannot yet access the support portal but need to raise a support issue, please use support@neo4j.com.

  4. Identified

    We are deploying a fix for the Aura Console so that Enterprise tier users can accept invites.

    We continue to progress on the data migration to the new customer portal.

    If you cannot yet access the support portal but need to raise a support issue, please use support@neo4j.com.

  5. Identified

    Aura Enterprise customers can now accept invites to Aura Console environments

    We are still progressing on the migration to our new customer portal.

    If you cannot yet access the support portal but need to raise a support issue, please use support@neo4j.com.

  6. Identified

    We are still progressing on the migration to our new customer portal. Many users have been migrated and activated, but not all have been processed. You will receive an email once your access has been migrated and activated.

    If you cannot yet access the support portal but need to raise a support issue, please use support@neo4j.com.

  7. Identified

    We are still progressing on the migration to our new customer portal. Many users have been migrated and activated, but not all have been processed. You will receive an email once your access has been migrated and activated.

    If you cannot yet access the support portal but need to raise a support issue, please use support@neo4j.com.

  8. Identified

    We are still progressing on the migration to our new customer portal. Many users have been migrated and activated, but not all have been processed. You will receive an email once your access has been migrated and activated.

    If you cannot yet access the support portal but need to raise a support issue, please use support@neo4j.com.

  9. Identified

    We are still progressing on the migration to our new customer portal. Many users have been migrated and activated, but not all have been processed. You will receive an email once your access has been migrated and activated.

    If you cannot yet access the support portal but need to raise a support issue, please use support@neo4j.com

  10. Identified

    We are still progressing on the migration to our new customer portal. Many users have been migrated and activated, but not all have been processed. You will receive an email once your access has been migrated and activated.

    If you cannot yet access the support portal but need to raise a support issue, please use support@neo4j.com

  11. Identified

    We are still progressing on the migration to our new customer portal. Many users have been migrated and activated, but not all have been processed. You will receive an email once your access has been migrated and activated.

    If you cannot yet access the support portal but need to raise a support issue, please use support@neo4j.com

  12. Identified

    We are still progressing on the migration to our new customer portal. Many users have been migrated and activated, but not all have been processed. You will receive an email once your access has been migrated and activated.

    If you cannot yet access the support portal but need to raise a support issue, please use support@neo4j.com

  13. Identified

    We are still progressing on the migration to our new customer portal. Most users have been migrated and activated, but some remain to be processed. You will receive an email once your access has been migrated and activated.

    If you cannot yet access the support portal but need to raise a support issue, please use support@neo4j.com.

  14. Identified

    We are still progressing on the migration to our new customer portal. Most users have been migrated and activated, but some remain to be processed. You will receive an email once your access has been migrated and activated.

    If you cannot yet access the support portal but need to raise a support issue, please use support@neo4j.com.

  15. Identified

    We are still progressing on the migration to our new customer portal. Most users have been migrated and activated, but some remain to be processed. You will receive an email once your access has been migrated and activated.

    If you cannot yet access the support portal but need to raise a support issue, please use support@neo4j.com.

  16. Identified

    We are still progressing on the migration to our new customer portal. Most users have been migrated and activated, but some remain to be processed. You will receive an email once your access has been migrated and activated.

    If you cannot yet access the support portal but need to raise a support issue, please use support@neo4j.com

  17. Identified

    We are still progressing on the migration to our new customer portal. Most users have been migrated and activated, but some remain to be processed. You will receive an email once your access has been migrated and activated.

    If you cannot yet access the support portal but need to raise a support issue, please use support@neo4j.com

  18. Identified

    We are still progressing on the migration to our new customer portal. Most users have been migrated and activated, but some remain to be processed. You will receive an email once your access has been migrated and activated.

    If you cannot yet access the support portal but need to raise a support issue, please use support@neo4j.com

  19. Identified

    We are still progressing on the migration to our new customer portal. Most users have been migrated and activated, but some remain to be processed. You will receive an email once your access has been migrated and activated.

    If you cannot yet access the support portal but need to raise a support issue, please use support@neo4j.com

  20. Identified

    We are still progressing on the migration to our new customer portal. Most users have been migrated and activated, but some remain to be processed. You will receive an email once your access has been migrated and activated.

    If you cannot yet access the support portal but need to raise a support issue, please use support@neo4j.com.

  21. Identified

    We are still progressing on the migration to our new customer portal. Most users have been migrated and activated, but some remain to be processed. You will receive an email once your access has been migrated and activated.

    If you cannot yet access the support portal but need to raise a support issue, please use support@neo4j.com.

  22. Identified

    We are still progressing on the migration to our new customer portal. Most users have been migrated and activated, but some remain to be processed. You will receive an email once your access has been migrated and activated.

    If you cannot yet access the support portal but need to raise a support issue, please use support@neo4j.com.

  23. Identified

    We are still progressing on the migration to our new customer portal. Most users have been migrated and activated, but some remain to be processed. You will receive an email once your access has been migrated and activated.

    If you cannot yet access the support portal but need to raise a support issue, please use support@neo4j.com

  24. Identified

    We are still progressing on the migration to our new customer portal. Most users have been migrated and activated, but some remain to be processed. You will receive an email once your access has been migrated and activated.

    If you cannot yet access the support portal but need to raise a support issue, please use support@neo4j.com

  25. Identified

    We are still progressing on the migration to our new customer portal. Most users have been migrated and activated, but some remain to be processed. You will receive an email once your access has been migrated and activated.

    If you cannot yet access the support portal but need to raise a support issue, please use support@neo4j.com

  26. Identified

    We are still progressing on the migration to our new customer portal. Most users have been migrated and activated, but some remain to be processed. You will receive an email once your access has been migrated and activated.

    If you cannot yet access the support portal but need to raise a support issue, please use support@neo4j.com

  27. Resolved

    Data migration is now completed successfully and the customer portal is functional.

    All registered users can sign-in to https://support.neo4j.com.

  28. Resolved

    ### What happened

    During the migration process from our legacy Support Portal to the new Customer Portal connected to our existing Customer Relationship Management (CRM) system, some customer records were merged in conflict with pre-existing records. As a result of this, the system rejected the login attempts from users with multiple records as a fail-safe. This resulted in a number of users receiving SSO sign-in errors when trying to access the Customer Portal.

    Once these initial conflicts had been resolved, some customer users were left detached from their organization which led the users not being able to see their organization data, such as users, projects and existing cases, and likewise could not open a new case without access to these organization-level records. At no time were any users able to see organization data to which they were not affiliated.

    ### How the service was affected

    A majority of Neo4j customers could not sign-in to the new customer portal which prevented access to existing support tickets or the raising of new tickets.

    The Neo4j Disaster Recovery (DR) procedures, leveraging email submissions to [support@neo4j.com](mailto:support@neo4j.com), was effective and allowed customers access to technical support resources. Email correspondence between Neo4j and customers on existing tickets was unaffected once a new thread was initiated by Neo4j Support.

    ### What we are doing now

    Whilst, through our DR procedure, we managed to keep the customer support service functioning, there were learnings leading to potential improvements to the DR procedures. Neo4j is in the process of updating the procedures to ensure the effectiveness when needed and to further improve on our ability to interact with customers in these rare situations.

    We strongly encourage all customers, with prior access to the legacy Support Portal, to verify login access to https://support.neo4j.com/s/, review a few KB articles describing the site, and confirm the ability to submit a new ticket. If login or case submission failures persist, email [support@neo4j.com](mailto:suppoort@neo4j.com) with details. All other customers should resume filing new tickets via the Customer Portal at https://support.neo4j.com/s/

Keep exploring

More from Neo4j Aura

Neighboring incidents on Neo4j Aura's timeline and the rest of their record on OutageDeck.