bgpreport

Network · data from 2026-11-12

AS150785 Polarish

Registry name: TWC-AS-AP - Polarish Co, HK · PeeringDB

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

Announced routes

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

2400:e3e0:a4e4::/48 No ROA Nonecovered by 2400:e3e0::/32 1 0%low visibility 1

AS-SET

AS150785'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 5 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none2400:e3e0:a4e4::/48No ROA covers it. Add a ROA for AS150785, maxLength 48.1 of 636
Route object: none2400:e3e0:a4e4::/48No route object for it. A route object for 2400:e3e0::/32 with origin AS150785 covers it (filters allowing more-specifics accept it). Add a route object with origin AS150785 in the RIR database for the space.1 of 636

Route objects not announced

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

85.149.223.0/24RADBValid
2400:e3e0::/32RADBNo ROA
2400:e3e0:c000::/36APNICValid

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.