bgpreport

Network · data from 2026-11-12

AS46959 VCC-AS - Vancouver Convention Centre

Registry name: VCC-AS - Vancouver Convention Centre, CA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS46959, 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.
2602:fac5::/42 No ROA Other IRR onlyBELL 634 100% 69
2602:fac5:40::/42 No ROA Other IRR onlyBELL 634 100% 69
2602:fac5:80::/42 No ROA Other IRR onlyRADB 634 100% 68
72.28.93.0/24 Valid Other IRR onlyRADB 670 100% 67
72.28.92.0/24 Valid Other IRR onlyRADB 665 99% 67
72.28.94.0/24 Valid Other IRR onlyRADB 665 99% 67
72.28.95.0/24 Valid Other IRR onlyRADB 665 99% 67

AS-SET

AS46959 isn't in PeeringDB, where networks name their 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 10 are in fix.csv.

  • ROA: none3
  • Route object: RIR7
ChangePrefix or setDetailFull-table peers
ROA: none2602:fac5::/42No ROA covers it. Add a ROA for AS46959, maxLength 42.634 of 636
Route object: RIR2602:fac5::/42Route object only in BELL. Add it in the RIR database for the space.634 of 636
ROA: none2602:fac5:40::/42No ROA covers it. Add a ROA for AS46959, maxLength 42.634 of 636
Route object: RIR2602:fac5:40::/42Route object only in BELL. Add it in the RIR database for the space.634 of 636
ROA: none2602:fac5:80::/42No ROA covers it. Add a ROA for AS46959, maxLength 42.634 of 636
Route object: RIR2602:fac5:80::/42Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR72.28.93.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR72.28.92.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR72.28.94.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR72.28.95.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673

Route objects not announced

Every route object with origin AS46959 is announced.

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.