bgpreport

Network · data from 2026-11-12

AS52941 SPACE NETWORK INFORMATICA

Registry name: AS52941 - SPACE NETWORK, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS52941, 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.

2804:b18:a00::/40 Valid Nonecovered by 2804:b18::/36 36 6%low visibility 14
2804:b18:5500::/40 Valid Nonecovered by 2804:b18::/33 36 6%low visibility 14
2804:b18:8400::/41 Valid Nonecovered by 2804:b18:8400::/40 36 6%low visibility 14
2804:b18:8800::/41 Valid Nonecovered by 2804:b18:8800::/40 36 6%low visibility 14
2804:b18:8f00::/40 Valid Nonecovered by 2804:b18:8000::/36 36 6%low visibility 14
45.169.212.0/22 Valid Other IRR onlyRADB 672 100% 67
45.169.212.0/23 Valid Other IRR onlyRADB 672 100% 67
45.169.212.0/24 Valid Other IRR onlyRADB 672 100% 67
45.169.213.0/24 Valid Other IRR onlyRADB 672 100% 67
45.169.214.0/23 Valid Other IRR onlyRADB 672 100% 67
45.169.214.0/24 Valid Other IRR onlyRADB 672 100% 67
45.169.215.0/24 Valid Other IRR onlyRADB 672 100% 67
177.38.40.0/21 Valid Other IRR onlyNTTCOM, RADB, TC 672 100% 67
177.38.40.0/23 Valid Other IRR onlyRADB 672 100% 67
177.38.40.0/24 Valid Other IRR onlyRADB 672 100% 67
177.38.41.0/24 Valid Other IRR onlyRADB 672 100% 67
177.38.42.0/23 Valid Other IRR onlyRADB 672 100% 67
177.38.42.0/24 Valid Other IRR onlyRADB 672 100% 67
177.38.43.0/24 Valid Other IRR onlyRADB 672 100% 67
177.38.44.0/23 Valid Other IRR onlyRADB 672 100% 67
177.38.44.0/24 Valid Other IRR onlyRADB 672 100% 67
177.38.45.0/24 Valid Other IRR onlyRADB 672 100% 67
177.38.46.0/23 Valid Other IRR onlyRADB 672 100% 67
177.38.46.0/24 Valid Other IRR onlyRADB 672 100% 67
177.38.44.0/22 Valid Other IRR onlyRADB 671 100% 67
177.38.47.0/24 Valid Other IRR onlyRADB 671 100% 67
2804:b18::/32 Valid Other IRR onlyRADB, TC 635 100% 67
2804:b18::/36 Valid Other IRR onlyRADB 36 6%low visibility 14
2804:b18::/44 Valid Other IRR onlyRADB 36 6%low visibility 14
2804:b18:80::/44 Valid Other IRR onlyRADB 36 6%low visibility 14
2804:b18:c0::/44 Valid Other IRR onlyRADB 36 6%low visibility 14
2804:b18:8400::/40 Valid Other IRR onlyRADB 36 6%low visibility 14
2804:b18:8800::/40 Valid Other IRR onlyRADB 36 6%low visibility 14
2804:b18:8c00::/40 Valid Other IRR onlyRADB 36 6%low visibility 14
2804:b18:c000::/36 Valid Other IRR onlyRADB 36 6%low visibility 14
2804:b18:c010::/44 Valid Other IRR onlyRADB 36 6%low visibility 14

AS-SET

PeeringDB's irr_as_set for AS52941: AS-SPACENETWORK. 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 (AS52941 isn't in the set, or no route object for AS52941 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 objectsAS52941 in itNot covered
AS-SPACENETWORK RADB2 member sets in no database: AS-FJTEC, AS262403:AS-CUSTOMERS-NETWAY 516761 Yes 0
NTTCOM (also) 291398 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 51 are in fix.csv.

  • Route object: none5
  • Route object: RIR31
  • AS-SET: missing member2
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
Route object: none2804:b18:a00::/40No route object for it. A route object for 2804:b18::/36 with origin AS52941 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52941 in the RIR database for the space.36 of 636
Route object: none2804:b18:5500::/40No route object for it. A route object for 2804:b18::/33 with origin AS52941 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52941 in the RIR database for the space.36 of 636
Route object: none2804:b18:8400::/41No route object for it. A route object for 2804:b18:8400::/40 with origin AS52941 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52941 in the RIR database for the space.36 of 636
Route object: none2804:b18:8800::/41No route object for it. A route object for 2804:b18:8800::/40 with origin AS52941 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52941 in the RIR database for the space.36 of 636
Route object: none2804:b18:8f00::/40No route object for it. A route object for 2804:b18:8000::/36 with origin AS52941 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52941 in the RIR database for the space.36 of 636
Route object: RIR45.169.212.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.169.212.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.169.212.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.169.213.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.169.214.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.169.214.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.169.215.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.38.40.0/21Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.38.40.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.38.40.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.38.41.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.38.42.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.38.42.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.38.43.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.38.44.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.38.44.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.38.45.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.38.46.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.38.46.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.38.44.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR177.38.47.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:b18::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:b18::/36Route object only in RADB. Add it in the RIR database for the space.36 of 636
Route object: RIR2804:b18::/44Route object only in RADB. Add it in the RIR database for the space.36 of 636
Route object: RIR2804:b18:80::/44Route object only in RADB. Add it in the RIR database for the space.36 of 636
Route object: RIR2804:b18:c0::/44Route object only in RADB. Add it in the RIR database for the space.36 of 636
Route object: RIR2804:b18:8400::/40Route object only in RADB. Add it in the RIR database for the space.36 of 636
Route object: RIR2804:b18:8800::/40Route object only in RADB. Add it in the RIR database for the space.36 of 636
Route object: RIR2804:b18:8c00::/40Route object only in RADB. Add it in the RIR database for the space.36 of 636
Route object: RIR2804:b18:c000::/36Route object only in RADB. Add it in the RIR database for the space.36 of 636
Route object: RIR2804:b18:c010::/44Route object only in RADB. Add it in the RIR database for the space.36 of 636
AS-SET: missing memberAS-SPACENETWORKAS-SPACENETWORK (RADB) lists AS-FJTEC; no IRR database read has it.
AS-SET: missing memberAS-SPACENETWORKAS-SPACENETWORK (RADB) lists AS262403:AS-CUSTOMERS-NETWAY; no IRR database read has it.

Route objects not announced

Route objects with origin AS52941 whose prefix no peer sees AS52941 announce. Many are kept on purpose (backup routes, space announced only in some places).

177.38.40.0/22RADBValid
2804:b18::/33RADBValid
2804:b18:80::/48RADBValid
2804:b18:84::/48RADBValid
2804:b18:88::/48RADBValid
2804:b18:8c::/48RADBValid
2804:b18:8000::/33RADBValid
2804:b18:8000::/36RADBValid
2804:b18:8000::/40RADBValid
2804:b18:8000::/48RADBValid
2804:b18:8008::/48RADBValid
2804:b18:8040::/44RADBValid
2804:b18:8080::/44RADBValid

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.