$ birdc show protocols "bgp_*"
BGP sessions
Transit providers, exchange points and direct peers: sessions listed by the operator, plus neighbours RIPE RIS sees in the global table, fetched live in your browser.
| name | peer as | type | family | state |
|---|---|---|---|---|
| querying stat.ripe.net… | ||||
$ curl -s rdap.arin.net/registry/entity/…
Address space
Blocks registered to AS403145's organization at ARIN, with what RIPE RIS sees announced and the RPKI status, fetched live in your browser.
| prefix | family | arin net | bgp | rpki | registered |
|---|---|---|---|---|---|
| querying rdap.arin.net… | |||||
$ cat /etc/bird/policy.d/*.conf
Routing policy
How AS403145 peers, what it accepts and what it drops.
Peering
Policy: open
Happy to peer at any shared exchange or over a direct session. Email the NOC with your ASN, IPs and location.
RPKI origin validation
Action: reject invalid
Routes that are RPKI-invalid are dropped on import. Every prefix this network originates is covered by a ROA.
IRR filtering
Action: filter
Peer announcements are filtered against prefix lists built from your registered IRR objects. Keep your as-set current.
Bogons & sanity
Action: reject
Bogon prefixes, bogon ASNs, too-specific routes and over-long AS paths never make it into the table.
Max-prefix
Source: PeeringDB
Per-session limits come from your PeeringDB record. Keep the values there accurate so the session stays up.
Before we peer
Status: required
A PeeringDB record, an IRR as-set or route objects, and a reachable NOC contact.
$ xdg-open https://bgp.tools/as/403145
Look it up
Independent views of AS403145: routing, registry and peering data.
$ mail -s "Peering request: AS403145" trobotham@airpost.pw
Peer with us
Peering requests, routing problems and abuse reports all reach the operator directly. Include your ASN and the prefixes involved.
- noctrobotham@airpost.pw
- abusetrobotham@airpost.pw
- peeringdbpeeringdb.com/asn/403145
- as-setAS403145
- operatorTerrance Robotham (TJR)