bgpreport

Network · data from 2026-11-12

AS5111 Aibo Link

Registry name: ALCL-AS-AP - Aibo Link Co., Ltd., JP · PeeringDB

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

Announced routes

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

80.47.64.0/19 Valid RIR databaseAPNIC 670 100% 68
80.47.95.0/24 Valid RIR databaseAPNIC 670 100% 68

AS-SET

AS5111'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 64 are in fix.csv.

  • Route object: not announced64

Route objects not announced

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

80.47.64.0/20APNICValid
80.47.64.0/21APNICValid
80.47.64.0/22APNICValid
80.47.64.0/23APNICValid
80.47.64.0/24APNICValid
80.47.65.0/24APNICValid
80.47.66.0/23APNICValid
80.47.66.0/24APNICValid
80.47.67.0/24APNICValid
80.47.68.0/22APNICValid
80.47.68.0/23APNICValid
80.47.68.0/24APNICValid
80.47.69.0/24APNICValid
80.47.70.0/23APNICValid
80.47.70.0/24APNICValid
80.47.71.0/24APNICValid
80.47.72.0/21APNICValid
80.47.72.0/22APNICValid
80.47.72.0/23APNICValid
80.47.72.0/24APNICValid
80.47.73.0/24APNICValid
80.47.74.0/23APNICValid
80.47.74.0/24APNICValid
80.47.75.0/24APNICValid
80.47.76.0/22APNICValid
80.47.76.0/23APNICValid
80.47.76.0/24APNICValid
80.47.77.0/24APNICValid
80.47.78.0/23APNICValid
80.47.78.0/24APNICValid
80.47.79.0/24APNICValid
80.47.80.0/20APNICValid
80.47.80.0/21APNICValid
80.47.80.0/22APNICValid
80.47.80.0/23APNICValid
80.47.80.0/24APNICValid
80.47.81.0/24APNICValid
80.47.82.0/23APNICValid
80.47.82.0/24APNICValid
80.47.83.0/24APNICValid
80.47.84.0/22APNICValid
80.47.84.0/23APNICValid
80.47.84.0/24APNICValid
80.47.85.0/24APNICValid
80.47.86.0/23APNICValid
80.47.86.0/24APNICValid
80.47.87.0/24APNICValid
80.47.88.0/21APNICValid
80.47.88.0/22APNICValid
80.47.88.0/23APNICValid
80.47.88.0/24APNICValid
80.47.89.0/24APNICValid
80.47.90.0/23APNICValid
80.47.90.0/24APNICValid
80.47.91.0/24APNICValid
80.47.92.0/22APNICValid
80.47.92.0/23APNICValid
80.47.92.0/24APNICValid
80.47.93.0/24APNICValid
80.47.94.0/23APNICValid
80.47.94.0/24APNICValid
156.9.112.0/22ARINValid
205.150.1.0/24ARINNo ROA
205.205.201.0/24ARINNo 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.