bgpreport

Network · data from 2026-11-12

AS199809 MAX-TEL Maxtel LLC

Registry name: MAX-TEL Maxtel LLC, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS199809, 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.
82.97.194.0/23 No ROA RIR databaseRIPE 673 100% 67
82.97.202.0/24 No ROA RIR databaseRIPE 673 100% 67
185.41.40.0/24 No ROA RIR databaseRIPE 673 100% 66
185.41.41.0/24 No ROA RIR databaseRIPE 673 100% 67
185.41.42.0/24 No ROA RIR databaseRIPE 673 100% 67
185.41.43.0/24 No ROA RIR databaseRIPE 673 100% 67
185.200.152.0/24 No ROA RIR databaseRIPE 673 100% 66
185.200.153.0/24 No ROA RIR databaseRIPE 673 100% 66
185.200.154.0/24 No ROA RIR databaseRIPE 673 100% 67
185.200.155.0/24 No ROA RIR databaseRIPE 673 100% 67
80.240.100.0/24 No ROA RIR databaseRIPE 672 100% 67
80.240.102.0/24 No ROA RIR databaseRIPE 672 100% 66
80.240.110.0/24 No ROA RIR databaseRIPE 672 100% 66
185.200.152.0/22 No ROA RIR databaseRIPE 2 0%low visibility 2

AS-SET

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

  • ROA: none14
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none82.97.194.0/23No ROA covers it. Add a ROA for AS199809, maxLength 23.673 of 673
ROA: none82.97.202.0/24No ROA covers it. Add a ROA for AS199809, maxLength 24.673 of 673
ROA: none185.41.40.0/24No ROA covers it. Add a ROA for AS199809, maxLength 24.673 of 673
ROA: none185.41.41.0/24No ROA covers it. Add a ROA for AS199809, maxLength 24.673 of 673
ROA: none185.41.42.0/24No ROA covers it. Add a ROA for AS199809, maxLength 24.673 of 673
ROA: none185.41.43.0/24No ROA covers it. Add a ROA for AS199809, maxLength 24.673 of 673
ROA: none185.200.152.0/24No ROA covers it. Add a ROA for AS199809, maxLength 24.673 of 673
ROA: none185.200.153.0/24No ROA covers it. Add a ROA for AS199809, maxLength 24.673 of 673
ROA: none185.200.154.0/24No ROA covers it. Add a ROA for AS199809, maxLength 24.673 of 673
ROA: none185.200.155.0/24No ROA covers it. Add a ROA for AS199809, maxLength 24.673 of 673
ROA: none80.240.100.0/24No ROA covers it. Add a ROA for AS199809, maxLength 24.672 of 673
ROA: none80.240.102.0/24No ROA covers it. Add a ROA for AS199809, maxLength 24.672 of 673
ROA: none80.240.110.0/24No ROA covers it. Add a ROA for AS199809, maxLength 24.672 of 673
ROA: none185.200.152.0/22No ROA covers it. Add a ROA for AS199809, maxLength 22.2 of 673

Route objects not announced

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

80.240.100.0/28RIPENo ROA
80.240.100.68/30RIPENo ROA
80.240.100.80/28RIPENo ROA
80.240.100.100/30RIPENo ROA
80.240.100.104/30RIPENo ROA
80.240.100.108/30RIPENo ROA
80.240.100.112/28RIPENo ROA
80.240.100.128/28RIPENo ROA
80.240.100.208/28RIPENo ROA
81.22.194.0/23RIPENo ROA
185.41.40.0/22RIPENo ROA
185.41.43.224/27RIPENo 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.