bgpreport

Network · data from 2026-11-12

AS203110 Voicenter LTD

Registry name: Voicenter-IL01 Voicenter LTD, IL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS203110, 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.
185.138.168.0/23 No ROA Nonecovered by 185.138.168.0/22 672 100% 67
185.138.168.0/24 Valid Nonecovered by 185.138.168.0/22 672 100% 67
185.138.169.0/24 Valid Nonecovered by 185.138.168.0/22 44 7%low visibility 25
185.138.170.0/24 Valid Nonecovered by 185.138.168.0/22 2 0%low visibility 2
185.138.171.0/24 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

AS203110'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 6 are in fix.csv.

  • ROA: none1
  • Route object: none4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none185.138.168.0/23No ROA covers it. Add a ROA for AS203110, maxLength 23.672 of 673
Route object: none185.138.168.0/23No route object for it. A route object for 185.138.168.0/22 with origin AS203110 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203110 in the RIR database for the space.672 of 673
Route object: none185.138.168.0/24No route object for it. A route object for 185.138.168.0/22 with origin AS203110 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203110 in the RIR database for the space.672 of 673
Route object: none185.138.169.0/24No route object for it. A route object for 185.138.168.0/22 with origin AS203110 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203110 in the RIR database for the space.44 of 673
Route object: none185.138.170.0/24No route object for it. A route object for 185.138.168.0/22 with origin AS203110 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203110 in the RIR database for the space.2 of 673

Route objects not announced

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

185.138.168.0/22RIPENo 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.