bgpreport

Network · data from 2026-11-12

AS268702

Not in the RIR AS name list · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268702, 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.
45.170.148.0/24 Invalid: origin Other origin only 2 0%low visibility 2
45.170.149.0/24 Invalid: origin Other origin only 2 0%low visibility 2
45.170.150.0/24 Invalid: origin Other origin only 2 0%low visibility 2
45.170.151.0/24 Invalid: origin Other origin only 2 0%low visibility 2
2804:5970::/32 No ROA Other IRR onlyRADB 1 0%low visibility 1

AS-SET

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

  • ROA: origin4
  • ROA: none1
  • Route object: none4
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: origin45.170.148.0/24ROAs covering it name AS265269, not AS268702. If AS268702 should announce it, add a ROA for AS268702.2 of 673
Route object: none45.170.148.0/24Route objects for it name AS265269. Add a route object with origin AS268702 in the RIR database for the space.2 of 673
ROA: origin45.170.149.0/24ROAs covering it name AS265269, not AS268702. If AS268702 should announce it, add a ROA for AS268702.2 of 673
Route object: none45.170.149.0/24Route objects for it name AS265269. Add a route object with origin AS268702 in the RIR database for the space.2 of 673
ROA: origin45.170.150.0/24ROAs covering it name AS265269, not AS268702. If AS268702 should announce it, add a ROA for AS268702.2 of 673
Route object: none45.170.150.0/24Route objects for it name AS265269. Add a route object with origin AS268702 in the RIR database for the space.2 of 673
ROA: origin45.170.151.0/24ROAs covering it name AS265269, not AS268702. If AS268702 should announce it, add a ROA for AS268702.2 of 673
Route object: none45.170.151.0/24Route objects for it name AS265269. Add a route object with origin AS268702 in the RIR database for the space.2 of 673
ROA: none2804:5970::/32No ROA covers it. Add a ROA for AS268702, maxLength 32.1 of 636
Route object: RIR2804:5970::/32Route object only in RADB. Add it in the RIR database for the space.1 of 636

Route objects not announced

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