bgpreport

Network · data from 2026-11-12

AS208949 hbing-as

Registry name: hbing-as HBING LIMITED, GB · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS208949, 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.
185.114.146.0/23 Invalid: origin Other origin only 3 0%low visibility 3
45.154.228.0/24 Invalid: origin Other origin only 2 0%low visibility 2
102.129.200.0/24 Valid Other IRR onlyRADB 673 100% 66
102.165.51.0/24 Valid Other IRR onlyRADB 673 100% 66
79.182.13.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
93.113.203.0/24 Valid RIR databaseRIPE 673 100% 67
185.149.233.0/24 Valid RIR databaseRIPE 673 100% 67
192.101.68.0/24 Valid RIR databaseARIN 673 100% 67
193.151.109.0/24 Valid RIR databaseRIPE 673 100% 67
195.211.191.0/24 Valid RIR databaseRIPE 673 100% 67
217.216.144.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
217.216.177.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
13.141.65.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
45.88.0.0/24 Valid RIR databaseRIPE 672 100% 66
45.148.145.0/24 Valid RIR databaseRIPE 672 100% 66
45.148.146.0/24 Valid RIR databaseRIPE 672 100% 66

AS-SET

AS208949'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 9 are in fix.csv.

  • ROA: origin2
  • Route object: none2
  • Route object: RIR2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: origin185.114.146.0/23ROAs covering it name AS209411, not AS208949. If AS208949 should announce it, add a ROA for AS208949.3 of 673
Route object: none185.114.146.0/23Route objects for it name AS209411. Add a route object with origin AS208949 in the RIR database for the space.3 of 673
ROA: origin45.154.228.0/24ROAs covering it name AS219335, not AS208949. If AS208949 should announce it, add a ROA for AS208949.2 of 673
Route object: none45.154.228.0/24Route objects for it name AS219335. Add a route object with origin AS208949 in the RIR database for the space.2 of 673
Route object: RIR102.129.200.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR102.165.51.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

102.129.140.0/24AFRINICInvalid: origin
154.16.23.0/24AFRINICInvalid: origin
217.216.231.0/24RADB, RIPEValid

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.