bgpreport

Network · data from 2026-11-12

AS40513

Not in the RIR AS name list · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS40513, 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.
203.86.144.0/24 No ROA RIR databaseAPNIC, NTTCOM 672 100% 67
167.206.209.0/24 Valid Other IRR onlyRADB 672 100% 67
103.88.43.0/24 Valid RIR databaseAPNIC 673 100% 67
108.179.58.0/24 Valid RIR databaseARIN, RADB 672 100% 67
84.45.50.0/24 Valid RIR databaseRIPE 660 98% 67
147.78.60.0/24 Valid RIR databaseRIPE 660 98% 67

AS-SET

AS40513 isn't in PeeringDB, where networks name their AS-SET.

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 21 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced19
ChangePrefix or setDetailFull-table peers
ROA: none203.86.144.0/24No ROA covers it. Add a ROA for AS40513, maxLength 24.672 of 673
Route object: RIR167.206.209.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

75.98.68.0/24RADBNo ROA
84.45.70.0/24RIPEValid
103.106.160.0/22RADBNo ROA
103.112.68.0/22RADBNo ROA
103.205.120.0/22RADBNo ROA
125.252.94.0/24REACHInvalid: origin
147.78.60.0/22RIPENo ROA
147.78.61.0/24RIPEValid
175.159.128.0/20RADBNo ROA
185.239.220.0/22RADBNo ROA
185.243.240.0/22RADBNo ROA
202.45.32.0/19RADBNo ROA
202.75.76.0/22RADBNo ROA
203.86.144.0/23NTTCOM, RADBNo ROA
203.86.145.0/24APNICNo ROA
203.188.92.0/23RADBNo ROA
203.188.113.0/24RADBNo ROA
203.188.116.0/24RADBNo ROA
209.160.248.0/24RADBNo ROA

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.