bgpreport

Network · data from 2026-11-12

AS203993 Global NOG Alliance

Registry name: GNA-DC1-AS S.J.M. Steffann, NL · PeeringDB

4IPv4 routes 100.0% RPKI valid · 100.0% with a route object
4IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS203993, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS203993, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
67.221.252.0/24 Valid Other IRR onlyALTDB 173 26% 37
67.221.253.0/24 Valid Other IRR onlyALTDB 173 26% 37
67.221.255.0/24 Valid Other IRR onlyALTDB 173 26% 37
2607:fae0:f001::/48 Valid Other IRR onlyALTDB 132 21% 31
2607:fae0:f00c::/48 Valid Other IRR onlyALTDB 132 21% 31
2607:fae0:f00d::/48 Valid Other IRR onlyALTDB 132 21% 31
185.54.92.0/23 Valid RIR databaseRIPE 663 99% 67
2a00:8642::/32 Valid RIR databaseRIPE 621 98% 67

AS-SET

PeeringDB's irr_as_set for AS203993: AS203993:AS-ALL. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS203993 isn't in the set, or no route object for AS203993 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS203993 in itNot covered
AS203993:AS-ALL RIPE 4245 Yes 0

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 6 are in fix.csv.

  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
Route object: RIR67.221.252.0/24Route object only in ALTDB. Add it in the RIR database for the space.173 of 673
Route object: RIR67.221.253.0/24Route object only in ALTDB. Add it in the RIR database for the space.173 of 673
Route object: RIR67.221.255.0/24Route object only in ALTDB. Add it in the RIR database for the space.173 of 673
Route object: RIR2607:fae0:f001::/48Route object only in ALTDB. Add it in the RIR database for the space.132 of 636
Route object: RIR2607:fae0:f00c::/48Route object only in ALTDB. Add it in the RIR database for the space.132 of 636
Route object: RIR2607:fae0:f00d::/48Route object only in ALTDB. Add it in the RIR database for the space.132 of 636

Route objects not announced

Every route object with origin AS203993 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.