bgpreport

Network · data from 2026-11-12

AS33973 Epam-AS Epam Systems FLLC

Registry name: Epam-AS Epam Systems FLLC, BY · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS33973, 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.
213.184.231.0/24 No ROA RIR databaseRIPE 673 100% 66
217.21.63.0/24 No ROA RIR databaseRIPE 673 100% 66
87.252.249.0/24 No ROA RIR databaseRIPE 672 100% 67
213.184.243.0/24 No ROA RIR databaseRIPE 671 100% 68
217.21.56.0/24 No ROA RIR databaseRIPE 671 100% 68
91.120.43.0/24 Valid RIR databaseRIPE 673 100% 67
2602:815::/48 Valid RIR databaseARIN 628 99% 67

AS-SET

AS33973 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 5 are in fix.csv.

  • ROA: none5
ChangePrefix or setDetailFull-table peers
ROA: none213.184.231.0/24No ROA covers it. Add a ROA for AS33973, maxLength 24.673 of 673
ROA: none217.21.63.0/24No ROA covers it. Add a ROA for AS33973, maxLength 24.673 of 673
ROA: none87.252.249.0/24No ROA covers it. Add a ROA for AS33973, maxLength 24.672 of 673
ROA: none213.184.243.0/24No ROA covers it. Add a ROA for AS33973, maxLength 24.671 of 673
ROA: none217.21.56.0/24No ROA covers it. Add a ROA for AS33973, maxLength 24.671 of 673

Route objects not announced

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