bgpreport

Network · data from 2026-11-12

AS49954 Zextel

Registry name: PROGRESSTECH Progress Technology LLC, RU · PeeringDB

3IPv4 routes 66.7% 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
3Route objects not announced registered with origin AS49954, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS49954, 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.
195.208.188.0/24 No ROA RIR databaseRIPE 671 100% 68
193.233.154.0/24 Valid RIR databaseRIPE 671 100% 68
193.233.159.0/24 Valid RIR databaseRIPE 671 100% 68

AS-SET

AS49954'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 4 are in fix.csv.

  • ROA: none1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none195.208.188.0/24No ROA covers it. Add a ROA for AS49954, maxLength 24.671 of 673

Route objects not announced

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

95.215.128.0/22RADBNo ROA
194.85.67.0/24RIPENo ROA
2001:678:f4::/48RIPENo 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.