bgpreport

Network · data from 2026-11-12

AS24881 Interphone Ukraine

Registry name: INTERPHONE-AS Interphone Ltd., RU · 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
2Route objects not announced registered with origin AS24881, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS24881, 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.
91.192.156.0/22 Invalid: origin None 2 0%low visibility 2
46.162.0.0/18 Valid RIR databaseRIPE 673 100% 66
193.111.156.0/22 Valid RIR databaseRIPE 673 100% 66

AS-SET

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

  • ROA: origin1
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin91.192.156.0/22ROAs covering it name AS203273, not AS24881. If AS24881 should announce it, add a ROA for AS24881.2 of 673
Route object: none91.192.156.0/22No route object for it. Add a route object with origin AS24881 in the RIR database for the space.2 of 673

Route objects not announced

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

91.197.236.0/22RIPENo ROA
195.214.236.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.