bgpreport

Network · data from 2026-11-12

AS44300 IPLS

Registry name: IPLS-AS LLC "IPLS", RU · PeeringDB

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

Announced routes

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

88.151.248.0/24 No ROA Nonecovered by 88.151.248.0/22 2 0%low visibility 1
46.29.208.0/21 No ROA RIR databaseRIPE 673 100% 66
88.151.248.0/21 No ROA RIR databaseRIPE 673 100% 66
176.56.48.0/21 No ROA RIR databaseRIPE 673 100% 66
185.6.164.0/22 No ROA RIR databaseRIPE 673 100% 66
188.95.104.0/21 No ROA RIR databaseRIPE 673 100% 66
2a03:17c0::/32 No ROA RIR databaseRIPE 636 100% 67

AS-SET

AS44300's PeeringDB record names no 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 16 are in fix.csv.

  • ROA: none7
  • Route object: none1
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none88.151.248.0/24No ROA covers it. Add a ROA for AS44300, maxLength 24.2 of 673
Route object: none88.151.248.0/24No route object for it. A route object for 88.151.248.0/22 with origin AS44300 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44300 in the RIR database for the space.2 of 673
ROA: none46.29.208.0/21No ROA covers it. Add a ROA for AS44300, maxLength 21.673 of 673
ROA: none88.151.248.0/21No ROA covers it. Add a ROA for AS44300, maxLength 21.673 of 673
ROA: none176.56.48.0/21No ROA covers it. Add a ROA for AS44300, maxLength 21.673 of 673
ROA: none185.6.164.0/22No ROA covers it. Add a ROA for AS44300, maxLength 22.673 of 673
ROA: none188.95.104.0/21No ROA covers it. Add a ROA for AS44300, maxLength 21.673 of 673
ROA: none2a03:17c0::/32No ROA covers it. Add a ROA for AS44300, maxLength 32.636 of 636

Route objects not announced

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

46.29.208.0/22RIPENo ROA
46.29.212.0/22RIPENo ROA
88.151.248.0/22RIPENo ROA
88.151.252.0/22RIPENo ROA
176.56.48.0/22RIPENo ROA
176.56.52.0/22RIPENo ROA
188.95.104.0/22RIPENo ROA
188.95.108.0/22RIPENo 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.