bgpreport

Network · data from 2026-11-12

AS213702

Not in the RIR AS name list · not in PeeringDB

8IPv4 routes 25.0% RPKI valid · 0.0% with a route object
0IPv6 routes
5RPKI invalid 5 origin · 0 maxLength
1No ROA 8 with no route object for this origin
7Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS213702, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS213702, 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.
89.125.43.0/24 Invalid: origin Other origin only 2 0%low visibility 2
93.123.39.0/24 Invalid: origin None 2 0%low visibility 2
95.164.53.0/24 Invalid: origin None 2 0%low visibility 2
95.164.55.0/24 Invalid: origin None 2 0%low visibility 2
153.52.77.0/24 Invalid: origin Other origin only 2 0%low visibility 2
195.66.27.0/24 No ROA None 2 0%low visibility 2
141.98.6.0/24 Valid Other origin only 130 19% 40
178.17.59.0/24 Valid Other origin only 2 0%low visibility 3

AS-SET

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

  • ROA: origin5
  • ROA: none1
  • Route object: none8
ChangePrefix or setDetailFull-table peers
ROA: origin89.125.43.0/24ROAs covering it name AS218731, not AS213702. If AS213702 should announce it, add a ROA for AS213702.2 of 673
Route object: none89.125.43.0/24Route objects for it name AS218731. Add a route object with origin AS213702 in the RIR database for the space.2 of 673
ROA: origin93.123.39.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS213702 should announce it, add a ROA for AS213702.2 of 673
Route object: none93.123.39.0/24No route object for it. Add a route object with origin AS213702 in the RIR database for the space.2 of 673
ROA: origin95.164.53.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS213702 should announce it, add a ROA for AS213702.2 of 673
Route object: none95.164.53.0/24No route object for it. Add a route object with origin AS213702 in the RIR database for the space.2 of 673
ROA: origin95.164.55.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS213702 should announce it, add a ROA for AS213702.2 of 673
Route object: none95.164.55.0/24No route object for it. Add a route object with origin AS213702 in the RIR database for the space.2 of 673
ROA: origin153.52.77.0/24ROAs covering it name AS218731, not AS213702. If AS213702 should announce it, add a ROA for AS213702.2 of 673
Route object: none153.52.77.0/24Route objects for it name AS218731. Add a route object with origin AS213702 in the RIR database for the space.2 of 673
ROA: none195.66.27.0/24No ROA covers it. Add a ROA for AS213702, maxLength 24.2 of 673
Route object: none195.66.27.0/24No route object for it. Add a route object with origin AS213702 in the RIR database for the space.2 of 673
Route object: none141.98.6.0/24Route objects for it name AS218731. Add a route object with origin AS213702 in the RIR database for the space.130 of 673
Route object: none178.17.59.0/24Route objects for it name AS49453, AS198486. Add a route object with origin AS213702 in the RIR database for the space.2 of 673

Route objects not announced

Every route object with origin AS213702 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.