Routing security
AS207613 NULLL
Hosting APNIC
Announcements
What this network originates
Every prefix observed with AS207613 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 2a09:11c0:201::/48 | RPKI valid | IRR | 34 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS207613 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 2a09:11c0:200::/44 | /48 | RIPENCC |
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 |
|---|---|---|---|
| AS34927 | iFog GmbH | Declared | not observed |
| AS41051 | Openfactory GmbH | 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 AS207613 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 |
|---|---|---|---|---|---|
| 2a09:11c0:200::/44 | RIPE | — | NULLL-MNT | 2020-02-03 | Not announced |
| 2a09:11c0:200::/48 | RIPE | — | NULLL-MNT | 2020-08-16 | Not announced |
| 2a09:11c0:202::/48 | RIPE | — | NULLL-MNT | 2020-08-16 | Not announced |
| 2a09:11c0:203::/48 | RIPE | — | NULLL-MNT | 2020-09-22 | Not announced |
| 2a09:11c0:204::/48 | RIPE | — | NULLL-MNT | 2020-09-22 | Not announced |
| 2a09:11c0:205::/48 | RIPE | — | NULLL-MNT | 2020-09-24 | Not announced |
| 2a09:11c0:201::/48 | RIPE | — | NULLL-MNT | 2020-08-16 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS207613 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-4IXP | RIPE | Lists AS207613 as a direct member |
AS-4IXP-RS | RIPE | Lists AS207613 as a direct member |
AS-4IXPV6 | RIPE | Lists AS207613 as a direct member |
AS-COMBAHTON-VR | RIPE | Lists AS207613 as a direct member |
AS-EVIX | ALTDB | Lists AS207613 as a direct member |
AS-HURRICANEV6 | RADB | Lists AS207613 as a direct member |
AS-IFOG | ALTDB | Lists AS207613 as a direct member |
AS-IFOG | RIPE | Lists AS207613 as a direct member |
AS-PREN | RIPE | Lists AS207613 as a direct member |
AS-RETN-ACTUAL-V6 | RIPE | Lists AS207613 as a direct member |
AS207613:AS-ALL | RIPE | Lists AS207613 as a direct member |
AS209533:AS-BGPTUNNEL | RIPE | Lists AS207613 as a direct member |
AS39533:AS-SET:AS207613 | RIPE | Lists AS207613 as a direct member |
AS41051:AS-PARTICIPANTS | RIPE | Lists AS207613 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.