bgpreport

Network · data from 2026-11-12

AS202475 Elechservice_Grup_SRL ELECHSERVICE-GRUP S.R.L

Registry name: Elechservice_Grup_SRL ELECHSERVICE-GRUP S.R.L, MD · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS202475, 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.
193.57.52.0/22 Invalid: origin Other origin only 10 1%low visibility 12
193.57.52.0/24 Valid RIR databaseRIPE 672 100% 66
193.57.53.0/24 Valid RIR databaseRIPE 672 100% 66

AS-SET

AS202475 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 2 are in fix.csv.

  • ROA: origin1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: origin193.57.52.0/22ROAs covering it name AS31252, not AS202475. If AS202475 should announce it, add a ROA for AS202475.10 of 673
Route object: none193.57.52.0/22Route objects for it name AS31252. Add a route object with origin AS202475 in the RIR database for the space.10 of 673

Route objects not announced

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