Skip to content

Incident detail

Customer using legacy MD5 password cannot connect through pgbouncer

Resolved incidentMajor

Timeline window

to

Outage alerts

Get alerted the next time Aiven breaks

Free email alerts for up to 5 providers — no card, live in about a minute. Paid plans add Slack, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Updates are normalized from the official source chronology so timeline changes remain easy to scan.

  1. Investigating

    We have identified an issue affecting our customer using legacy MD5 password cannot connect through pgbouncer.

    Our engineering team is actively working to identify the root cause and restore the service.

    We appreciate your patience and will share another update once we have identified the issue.

  2. Investigating

    Our engineering team is still actively working to identify the root cause.

    We appreciate your patience and will share another update once we have identified the issue.

  3. Identified

    We have identified the root cause of the issue affecting the services.

    We are actively working to resolve this issue.

    We apologise for the inconvenience caused by this issue. We will provide a further update in approximately 30 minutes.

  4. Monitoring

    We have identified the root cause of the issue and are currently rolling out a mitigation to affected customers.

    We expect the issue to be resolved soon.

    Please reach out to the Aiven support team if you're still encountering issues connecting through PGBouncer.

  5. Resolved

    We have resolved the underlying cause of issue affecting our customers using legacy MD5 password cannot connect through pgbouncer.

    Should any further issues be encountered, please reach out to support via the Aiven console.

    We apologise for the inconvenience caused by this issue, and commit to analysing and improving our platform to avoid future incidents similar to this one.