bgpreport

Network · data from 2026-11-12

AS48873 proxi-com LLC "Proxicom"

Registry name: proxi-com LLC "Proxicom", RU · not in PeeringDB

12IPv4 routes 41.7% RPKI valid · 91.7% with a route object
0IPv6 routes
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
9Route objects not announced registered with origin AS48873, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS48873, 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.
95.129.176.0/21 No ROA RIR databaseRIPE 671 100% 66
95.129.176.0/22 No ROA RIR databaseRIPE 671 100% 66
95.129.177.0/24 No ROA RIR databaseRIPE 671 100% 66
95.129.179.0/24 No ROA RIR databaseRIPE 671 100% 66
95.129.180.0/22 No ROA RIR databaseRIPE 671 100% 66
95.129.182.0/24 No ROA RIR databaseRIPE 671 100% 66
95.129.183.0/24 No ROA RIR databaseRIPE 671 100% 66
45.142.32.0/23 Valid Nonecovered by 45.142.32.0/22 671 100% 66
45.142.32.0/24 Valid RIR databaseRIPE 670 100% 66
45.142.33.0/24 Valid RIR databaseRIPE 670 100% 66
45.142.34.0/24 Valid RIR databaseRIPE 670 100% 66
45.142.32.0/22 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

AS48873 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 17 are in fix.csv.

  • ROA: none7
  • Route object: none1
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none95.129.176.0/21No ROA covers it. Add a ROA for AS48873, maxLength 21.671 of 673
ROA: none95.129.176.0/22No ROA covers it. Add a ROA for AS48873, maxLength 22.671 of 673
ROA: none95.129.177.0/24No ROA covers it. Add a ROA for AS48873, maxLength 24.671 of 673
ROA: none95.129.179.0/24No ROA covers it. Add a ROA for AS48873, maxLength 24.671 of 673
ROA: none95.129.180.0/22No ROA covers it. Add a ROA for AS48873, maxLength 22.671 of 673
ROA: none95.129.182.0/24No ROA covers it. Add a ROA for AS48873, maxLength 24.671 of 673
ROA: none95.129.183.0/24No ROA covers it. Add a ROA for AS48873, maxLength 24.671 of 673
Route object: none45.142.32.0/23No route object for it. A route object for 45.142.32.0/22 with origin AS48873 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48873 in the RIR database for the space.671 of 673

Route objects not announced

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

45.142.35.0/24RIPEValid
95.129.176.0/23RIPENo ROA
95.129.176.0/24RIPENo ROA
95.129.178.0/23RIPENo ROA
95.129.178.0/24RIPENo ROA
95.129.180.0/23RIPENo ROA
95.129.180.0/24RIPENo ROA
95.129.181.0/24RIPENo ROA
95.129.182.0/23RIPENo 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.