# Supabase is now on Postgres 13.3

[Supabase](https://yomu.fyi/company/supabase) · Angelico de los Reyes · Jul 26, 2021

**Type:** Announcement

## Summary

New Supabase projects now run on Supabase Postgres 13.3, transitioning the database platform forward from PostgreSQL 12.0. This release introduces features such as native UUID generation with gen\_random\_uuid, parallel index vacuuming, incremental sorting, smaller btree indexes, and extended statistics improvements. The underlying PostgreSQL binary was built from the ground up to enable Large System Extensions on AWS Graviton2 ARM instances, optimizing locking and synchronization performance. Alongside upgrading the underlying operating system to Ubuntu 20.04 for long-term support through 2025, the team integrated fail2ban to protect direct database connections on ports 5432 and 6543 against brute-force attacks. Finally, Supabase Postgres version numbering now mirrors upstream PostgreSQL major and minor versions to make tracking installed releases easier.

## Context

Supabase needed to upgrade from PostgreSQL 12.0 and Ubuntu 18.04 to deliver new database functionality, extend operating system support through 2025, enable Large System Extensions on AWS Graviton2 hardware, and protect database instances from brute-force connection attempts.

## Approach / What changed

Supabase built PostgreSQL 13.3 from source to enable LSE support for ARM instances, updated the base operating system to Ubuntu 20.04, aligned repository versioning to track upstream PostgreSQL release numbers, and configured fail2ban on ports 5432 and 6543 to ban IPs for 10 minutes after three failed attempts.

## Takeaways

- Supabase Postgres version numbering now mirrors PostgreSQL major and minor releases directly, with patch version bumps applied when releases occur between upstream updates.
- Building PostgreSQL from source enabled Large System Extensions on AWS Graviton2 instances, utilizing atomics to improve locking and synchronization performance.
- Direct database connections on port 5432 for PostgreSQL and port 6543 for PgBouncer are now protected by fail2ban, banning IP addresses for 10 minutes after three failed login attempts.

**Tags:** [AWS](https://yomu.fyi/topic/aws), [Performance](https://yomu.fyi/topic/performance), [Postgres](https://yomu.fyi/topic/postgres)

[Read original post](https://supabase.com/blog/supabase-postgres-13)