bgpreport

Network · data from 2026-11-12

AS208862 SIRINFO

Registry name: SIRINFO-AS SIRIANNI INFORMATICA S.R.L. IN SIGLA SIRINFO S.R.L., IT · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS208862, 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.

5.83.108.0/24 Valid Nonecovered by 5.83.108.0/22 672 100% 66
5.83.109.0/24 Valid Nonecovered by 5.83.108.0/22 672 100% 66
5.83.110.0/24 Valid Nonecovered by 5.83.108.0/22 672 100% 66
5.83.111.0/24 Valid Nonecovered by 5.83.108.0/22 672 100% 66
5.83.108.0/22 Valid RIR databaseRIPE 673 100% 66
45.82.0.0/22 Valid RIR databaseRIPE 673 100% 66
5.83.105.0/24 Valid RIR databaseRIPE 672 100% 66
5.83.106.0/24 Valid RIR databaseRIPE 672 100% 66
5.83.107.0/24 Valid RIR databaseRIPE 672 100% 66
45.82.0.0/24 Valid RIR databaseRIPE 672 100% 66
45.82.1.0/24 Valid RIR databaseRIPE 672 100% 66
45.82.2.0/24 Valid RIR databaseRIPE 672 100% 66
45.82.3.0/24 Valid RIR databaseRIPE 672 100% 66

AS-SET

AS208862'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.

  • Route object: none4
ChangePrefix or setDetailFull-table peers
Route object: none5.83.108.0/24No route object for it. A route object for 5.83.108.0/22 with origin AS208862 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208862 in the RIR database for the space.672 of 673
Route object: none5.83.109.0/24No route object for it. A route object for 5.83.108.0/22 with origin AS208862 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208862 in the RIR database for the space.672 of 673
Route object: none5.83.110.0/24No route object for it. A route object for 5.83.108.0/22 with origin AS208862 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208862 in the RIR database for the space.672 of 673
Route object: none5.83.111.0/24No route object for it. A route object for 5.83.108.0/22 with origin AS208862 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208862 in the RIR database for the space.672 of 673

Route objects not announced

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