bgpreport

Network · data from 2026-11-12

AS49188 Three A Hub

Registry name: Three-A-Hub Three A Hub EOOD, BG · PeeringDB

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

Announced routes

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

78.108.250.0/24 No ROA RIR databaseRIPE 672 100% 66
109.160.68.0/24 No ROA RIR databaseRIPE 672 100% 66
109.160.78.0/24 No ROA RIR databaseRIPE 672 100% 66
109.160.79.0/24 No ROA RIR databaseRIPE 672 100% 66
109.160.80.0/24 No ROA RIR databaseRIPE 672 100% 66
2a10:9d00::/29 Valid None 631 99% 67
78.128.4.0/24 Valid RIR databaseRIPE 673 100% 66
185.163.244.0/22 Valid RIR databaseRIPE 673 100% 66
185.163.244.0/24 Valid RIR databaseRIPE 673 100% 66
185.163.245.0/24 Valid RIR databaseRIPE 673 100% 66
185.163.246.0/24 Valid RIR databaseRIPE 673 100% 66
95.169.197.0/24 Valid RIR databaseRIPE 672 100% 66
95.169.198.0/24 Valid RIR databaseRIPE 672 100% 66

AS-SET

AS49188'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 12 are in fix.csv.

  • ROA: none5
  • Route object: none1
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none78.108.250.0/24No ROA covers it. Add a ROA for AS49188, maxLength 24.672 of 673
ROA: none109.160.68.0/24No ROA covers it. Add a ROA for AS49188, maxLength 24.672 of 673
ROA: none109.160.78.0/24No ROA covers it. Add a ROA for AS49188, maxLength 24.672 of 673
ROA: none109.160.79.0/24No ROA covers it. Add a ROA for AS49188, maxLength 24.672 of 673
ROA: none109.160.80.0/24No ROA covers it. Add a ROA for AS49188, maxLength 24.672 of 673
Route object: none2a10:9d00::/29No route object for it. Add a route object with origin AS49188 in the RIR database for the space.631 of 636

Route objects not announced

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

185.163.246.0/23RIPEValid
185.163.247.0/24RIPEInvalid: maxLength
2a10:9d00::/48RIPEValid
2a10:9d00:1::/48RIPEValid
2a10:9d00:2::/48RIPEValid
2a10:9d00:3::/48RIPEValid

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.