Routing security
AS203991 AS20473
Unclassified RIPE
Announcements
What this network originates
Every prefix observed with AS203991 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 2a13:e5c0:ee02::/48 | No ROA | IRR | 35 |
| 2a14:67c3:8800::/44 | No ROA | IRR | 35 |
| 44.30.149.0/24 | No ROA | IRR | 54 |
| 2602:f486:f0::/48 | RPKI valid | IRR | 35 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS203991 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 2602:f486:f0::/48 | /48 | ARIN |
ROA-based and RPKI-valid-only prefix lists for routers are on asn.ipinfo.app.
RPKI · ASPA
Declared transit providers
This network has signed an ASPA record naming its transit providers. Each is compared against the upstreams observed in routing paths.
| AS | Network | ASPA | Routing paths |
|---|---|---|---|
| AS20473 | The Constant Company, LLC | Declared | Observed |
| AS41051 | Openfactory GmbH | Declared | Observed |
| AS209533 | iFog GmbH | not declared | Observed |
An observed upstream that is not declared is not necessarily a leak: our upstream inference cannot tell a transit provider from a peer seen in the same position. A declared provider that is never observed is usually a backup path.
IRR
Registered route objects
Route objects naming AS203991 as origin, across RADb, the RIR registries, ALTDB and NTTCOM. Objects that are registered but not announced come first: a stale object lets anyone who can spoof this origin through an IRR-built filter.
| Prefix | Source | Description | Maintainer | Changed | Routing |
|---|---|---|---|---|---|
| 44.30.121.0/24 | RADB | BD1DKW | MAINT-ARDC | 2026-08-27 | Not announced |
| 44.30.149.0/24 | RADB | BI4KWC | MAINT-ARDC | 2026-06-05 | Announced |
| 2602:f486:f0::/48 | ARIN | Geoscry Network LLC | MNT-GNL-57 | 2026-06-11 | Announced |
| 2602:f486:f0::/48 | RADB | Vultr Customer Route | MAINT-AS20473 | 2026-09-26 | Announced |
| 2a13:e5c0:ee02::/48 | RADB | Vultr Customer Route | MAINT-AS20473 | 2026-08-24 | Announced |
| 2a14:67c3:8800::/44 | RADB | Vultr Customer Route | MAINT-AS20473 | 2026-09-01 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS203991 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-COTA | RIPE | Lists AS203991 as a direct member |
AS-E1-AUTOMATION-CUSTOMER | RADB | Lists AS203991 as a direct member |
AS-HURRICANEV6 | RADB | Lists AS203991 as a direct member |
AS-RETN-ACTUAL-V4 | RIPE | Lists AS203991 as a direct member |
AS-RETN-ACTUAL-V6 | RIPE | Lists AS203991 as a direct member |
AS-XJP | ARIN | Lists AS203991 as a direct member |
AS20473:AS-VULTR | RADB | Lists AS203991 as a direct member |
AS209533:AS-BGPTUNNEL | RIPE | Lists AS203991 as a direct member |
AS41051:AS-PARTICIPANTS | RIPE | Lists AS203991 as a direct member |
RPKI from rpki-client, validated 2026-10-13 12:16 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-13. Cross-check on bgp.he.net.