bgpreport

Network · data from 2026-11-12

AS8585 INTERNET-CG Crnogorski Telekom a.d.Podgorica

Registry name: INTERNET-CG Crnogorski Telekom a.d.Podgorica, ME · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS8585, 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.
195.66.164.0/24 Valid Nonecovered by 195.66.160.0/19 671 100% 68
195.66.180.0/24 Valid Nonecovered by 195.66.160.0/19 671 100% 68
195.66.189.0/24 Valid Nonecovered by 195.66.160.0/19 671 100% 68
31.204.192.0/18 Valid RIR databaseRIPE 671 100% 68
37.122.160.0/19 Valid RIR databaseRIPE 671 100% 68
46.33.192.0/19 Valid RIR databaseRIPE 671 100% 68
46.161.64.0/18 Valid RIR databaseRIPE 671 100% 68
77.222.0.0/19 Valid RIR databaseRIPE 671 100% 68
78.155.32.0/19 Valid RIR databaseRIPE 671 100% 68
85.94.96.0/19 Valid RIR databaseRIPE 671 100% 68
95.155.0.0/18 Valid RIR databaseRIPE 671 100% 68
109.228.64.0/18 Valid RIR databaseRIPE 671 100% 68
195.66.160.0/19 Valid RIR databaseRIPE 671 100% 68
213.149.96.0/19 Valid RIR databaseRIPE 671 100% 68
2a00:fe80::/32 Valid RIR databaseRIPE 635 100% 68

AS-SET

AS8585 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 3 are in fix.csv.

  • Route object: none3
ChangePrefix or setDetailFull-table peers
Route object: none195.66.164.0/24No route object for it. A route object for 195.66.160.0/19 with origin AS8585 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8585 in the RIR database for the space.671 of 673
Route object: none195.66.180.0/24No route object for it. A route object for 195.66.160.0/19 with origin AS8585 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8585 in the RIR database for the space.671 of 673
Route object: none195.66.189.0/24No route object for it. A route object for 195.66.160.0/19 with origin AS8585 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8585 in the RIR database for the space.671 of 673

Route objects not announced

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