asn.dev

Routing security

AS40623 GFDL

Unclassified ARIN

RPKI valid 100% 4 of 4 announcements
RPKI invalid 0 none
No ROA 0 not covered by any ROA
IRR registered 100% 0 missing · 0 other origin
ROAs 4 authorising this AS

Announcements

What this network originates

4 observed

Every prefix observed with AS40623 as its origin, checked against RPKI and the IRR. Problems sort first.

PrefixRPKIIRRVantage points
140.208.0.0/18RPKI validIRR54
140.208.144.0/20RPKI validIRR54
2610:20:8020::/44RPKI validIRR29
2610:20:9120::/48RPKI validIRR29

RPKI · ROAs

Route origin authorisations

4 ROAs

Signed statements by address holders that AS40623 may originate these prefixes, up to the maximum length shown.

PrefixMax lengthTrust anchor
140.208.0.0/18/18ARIN
140.208.144.0/20/20ARIN
2610:20:8020::/44/44ARIN
2610:20:9120::/48/48ARIN

ROA-based and RPKI-valid-only prefix lists for routers are on asn.ipinfo.app.

RPKI · ASPA

Declared transit providers

No ASPA record This network has not published an ASPA object. ASPA lets a network sign the list of its transit providers, so routers can reject paths that route through anyone else (route leaks). Only a few thousand networks publish one so far, so its absence is normal.

IRR

Registered route objects

4 objects · 0 not announced

Route objects naming AS40623 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.

PrefixSourceDescriptionMaintainerChangedRouting
140.208.0.0/18ARINGFDLNETMNT-GFDL-Z2025-04-28Announced
140.208.144.0/20ARINRDHPCS Princeton 2MNT-GFDL-Z2025-04-28Announced
2610:20:8020::/44ARINGFDL, Princeton, NJMNT-NOAABO2024-07-02Announced
2610:20:9120::/48ARINRDHPCS GFDLMNT-NOAABO2024-07-02Announced

IRR

AS-sets

The as-set is what upstreams expand to build this network's customer filter. Sets that list AS40623 directly show who expects to carry it.

AS-setWhereRelationship
AS-3477-ALLARINLists AS40623 as a direct member

RPKI from rpki-client, validated 2026-10-22 12:01 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-22. Cross-check on bgp.he.net.