3AM Network
online
An Internet Exchange.

AS202301

site QUPRA DC · Amsterdam · NL
state route server up · live ▸
For small ASNs and weird ideas. Peering as it should be — expensive open, plain text, fewer meetings.
01

Manifesto_

The internet got boring. Big transit, big peering rooms, big rate cards. We don't run any of those. We run this.

3AM Network is an open exchange for the smallest ASNs and the weirdest projects. If you got a /24 in 2025 because somebody on a forum had a spare, if your «router» is a $30 box on a kitchen shelf, if you read RFCs for fun — you belong on the fabric.

We exist for home networks brave enough to apply for an ASN, students learning BGP from PCAPs, and people who think peering meetings still belong at 3 am after a few beers. We are not a startup. We are not a non-profit. We are an exchange.

  • Open peering by default. Route server first, bilateral if you must.
  • IPv6 not as marketing. As the default.
  • RPKI required. Bogons rejected without remorse.
  • No member dues, no setup fee, no annual gala dinner.
  • If you break the fabric, we will write a postmortem. With your name in it.
02

Participants

0 dues open peering
ASN Organisation Address Connected Link
AS26954 Mikhail Fedorov
91.213.211.69
2001:7f8:17d::69
2026-05-15 10G
AS11967 Hop179 OU
91.213.211.70
2001:7f8:17d::70
2026-05-16 10G
AS402536 NETZR LLC
91.213.211.71
2001:7f8:17d::71
2026-05-19 1G
AS214630 Kyberorg IT OU
91.213.211.72
2001:7f8:17d::72
2026-05-20 10G
AS215887 Baragoon Networks
91.213.211.73
2001:7f8:17d::73
2026-05-20 1G
AS213449 JOW
91.213.211.74
2001:7f8:17d::74
2026-05-20 10G
AS213409 Lynqia Network
91.213.211.75
2001:7f8:17d::75
2026-05-21 10G
AS204539 Axivora Connect LtD
91.213.211.76
2001:7f8:17d::76
2026-05-26 10G
AS197324 BGP43
91.213.211.77
2001:7f8:17d::77
2026-05-27 10G
AS210464 AVS ISP
91.213.211.78
2001:7f8:17d::78
2026-06-09
10G
MANRS
AS215760 DisPaisy Enterprises
91.213.211.79
2001:7f8:17d::79
2026-06-06 10G
AS215296 LowPing NL
91.213.211.80
2001:7f8:17d::80
2026-06-13 10G
AS215248 Bastiaan Mathijs Brink
91.213.211.81
2001:7f8:17d::81
2026-06-13 10G
03

Peering

Route Servers

primary fabric
ASN
AS202301
rs1 IPv4
91.213.211.65
rs1 IPv6
2001:7f8:17d::65
rs2 IPv4
91.213.211.66
rs2 IPv6
2001:7f8:17d::66
MD5
none — this is 2026
MTU
1500 (jumbo on request)
BFD
supported

Requirements

read before you ask
  1. A real ASN. A real prefix. RIR-issued, not vibes.
  2. PeeringDB record updated this decade.
  3. RPKI ROAs published for everything you'll announce.
  4. One BGP session, one operator email that humans actually read.
  5. Your own + customer-cone prefixes only. No default route, no full DFZ. A Tier-1 transit ASN anywhere in your AS_PATH means you're leaking — rejected.
  6. Layer-2 hygiene on the fabric: only IPv4, IPv6, ARP, NDP. STP/CDP/LLDP/DHCP/RA/everything else is dropped.

Request peering

[email protected]
  • ASN and the org behind it
  • Prefixes you'll announce (with ROAs published)
  • AS-SET name (we filter from it) or just AS number
  • 24/7 operator email AND phone — both reach a human
  • PeeringDB profile link

BGP Large Communities

RFC 8092
202301:0:0Do not announce to any peer
202301:1:0Announce to all (default)
202301:666:0Blackhole this prefix
202301:1:<peer-as>Announce only to this peer
202301:0:<peer-as>Exclude this peer

AS112

anycast · RFC 7534
prefixes
192.175.48.0/24
192.31.196.0/24
2620:4f:8000::/48
2001:4:112::/48
peering
91.213.211.112
2001:7f8:17d::112
purpose
Sinks reverse-DNS queries for RFC 1918 and similar private space — keeps that traffic off the root servers.
info
as112.net ↗

Better internet

  • RS filtering. RPKI ROV (drop INVALID) + per-member prefix-lists from your AS-SET via bgpq4 + bogon / length / max-prefix. Filters refresh daily.
  • Coordination. [email protected] reaches a human. Telegram is open. Members listed in /export.json.
  • Tools. Looking glass at lg.3am.network — both route servers and the AS112 sink.
  • Aligned with the MANRS IXP framework.
04

Policy

Peering Policy

Open. The route server will accept your session if the boxes below are checked. We do not negotiate. We do not have an account manager. You either match the policy or you don't.

  • Origin AS validation: RPKI valid + IRR present
  • Max-prefix: your PeeringDB-declared count. Keep PeeringDB current.
  • No prefix shorter than /24 (v4) or /48 (v6)
  • No prefixes you don't hold. Yes, we check.

Anti-Abuse

If your prefix is the source of spam, scans, amplification, or any flavour of traffic that the operator community quietly dislikes, the route server will quietly stop accepting it.

  • One warning, one hour. Then filter.
  • Repeated abuse: indefinite filter + the postmortem mentioned earlier.
  • Reports: [email protected] — read by a human.
  • RPKI invalid? Rejected. Bogon? Rejected. AS_PATH containing <our ASN>? Definitely rejected.

Acceptable Use

The fabric is for routing packets. It is not for tunneling around your transit's filter, hosting a control plane for a botnet, or "stress testing" anyone. Use the internet the way it was meant: badly, but with intent.

Routing Hygiene

We do our part: filter at the route server, drop ROA-invalid, run a real looking glass, answer the phone. We expect the same from you on your network. Publish ROAs for every prefix you announce. Keep your IRR objects current. Filter your own customers. Don't leak transit. Run BCP38 at the edge. None of this is optional, all of it is doable on a weekend, and it makes the internet measurably less broken.

05

Resources