bgpreport

Network · data from 2026-11-12

AS216300 AbkhazMedia-As Closed Joint Stock Company "AbkhazMedia"

Registry name: AbkhazMedia-As Closed Joint Stock Company "AbkhazMedia", GE · not in PeeringDB

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

Announced routes

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

45.12.63.0/24 Invalid: origin None 2 0%low visibility 2
45.147.31.0/24 Invalid: origin None 2 0%low visibility 2
77.221.144.0/24 No ROA RIR databaseRIPE 2 0%low visibility 2
194.31.73.0/24 Valid Other origin only 671 100% 68
77.221.135.0/24 Valid Other origin only 1 0%low visibility 1
179.254.97.0/24 Valid RIR databaseRIPE 673 100% 67
45.12.68.0/24 Valid RIR databaseRIPE 671 100% 68
77.105.130.0/24 Valid RIR databaseRIPE 671 100% 68
77.105.135.0/24 Valid RIR databaseRIPE 671 100% 68
77.105.161.0/24 Valid RIR databaseRIPE 671 100% 68
78.40.211.0/24 Valid RIR databaseRIPE 671 100% 68
94.159.112.0/24 Valid RIR databaseRIPE 671 100% 68
94.159.114.0/24 Valid RIR databaseRIPE 671 100% 68
132.243.202.0/24 Valid RIR databaseRIPE 671 100% 68
132.243.206.0/24 Valid RIR databaseRIPE 671 100% 68
132.243.226.0/24 Valid RIR databaseRIPE 671 100% 68
185.225.203.0/24 Valid RIR databaseRIPE 671 100% 68
193.163.170.0/24 Valid RIR databaseRIPE 671 100% 68
194.50.153.0/24 Valid RIR databaseRIPE 671 100% 68
2a12:b3c0:3::/48 Valid RIR databaseRIPE 636 100% 69
77.105.164.0/24 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

AS216300 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 17 are in fix.csv.

  • ROA: origin2
  • ROA: none1
  • Route object: none4
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: origin45.12.63.0/24ROAs covering it name AS213334, not AS216300. If AS216300 should announce it, add a ROA for AS216300.2 of 673
Route object: none45.12.63.0/24No route object for it. Add a route object with origin AS216300 in the RIR database for the space.2 of 673
ROA: origin45.147.31.0/24ROAs covering it name AS213334, not AS216300. If AS216300 should announce it, add a ROA for AS216300.2 of 673
Route object: none45.147.31.0/24No route object for it. Add a route object with origin AS216300 in the RIR database for the space.2 of 673
ROA: none77.221.144.0/24No ROA covers it. Add a ROA for AS216300, maxLength 24.2 of 673
Route object: none194.31.73.0/24Route objects for it name AS204339. Add a route object with origin AS216300 in the RIR database for the space.671 of 673
Route object: none77.221.135.0/24Route objects for it name AS216024. Add a route object with origin AS216300 in the RIR database for the space.1 of 673

Route objects not announced

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

45.87.121.0/24RIPEValid
77.105.128.0/24RIPEValid
77.105.129.0/24RIPEValid
77.105.132.0/24RIPEValid
77.105.134.0/24RIPEValid
77.105.160.0/24RIPEValid
185.225.202.0/24RIPEValid
2a12:b3c0::/48RIPEValid
2a12:b3c0:2::/48RIPEValid
2a12:b3c0:4::/48RIPENo 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.