bgpreport

Network · data from 2026-11-12

AS6561 Juce Communications Inc.

Registry name: JUCE - JUCE Communications Inc, CA · PeeringDB

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

Announced routes

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

104.142.0.0/17 No ROA RIR databaseARIN 669 99% 68
104.142.48.0/20 No ROA RIR databaseARIN 669 99% 68
104.142.64.0/19 No ROA RIR databaseARIN 669 99% 68
104.142.96.0/21 No ROA RIR databaseARIN 669 99% 68
104.142.104.0/22 No ROA RIR databaseARIN 669 99% 68
104.142.111.0/24 No ROA RIR databaseARIN 669 99% 68
104.142.112.0/20 No ROA RIR databaseARIN 669 99% 68
104.163.0.0/17 No ROA RIR databaseARIN 669 99% 68

AS-SET

PeeringDB's irr_as_set for AS6561: ARIN::AS-6561-AS-ALL. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS6561 isn't in the set, or no route object for AS6561 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS6561 in itNot covered
ARIN::AS-6561-AS-ALL ARIN 129 Yes 0

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: none8
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none104.142.0.0/17No ROA covers it. Add a ROA for AS6561, maxLength 17.669 of 673
ROA: none104.142.48.0/20No ROA covers it. Add a ROA for AS6561, maxLength 20.669 of 673
ROA: none104.142.64.0/19No ROA covers it. Add a ROA for AS6561, maxLength 19.669 of 673
ROA: none104.142.96.0/21No ROA covers it. Add a ROA for AS6561, maxLength 21.669 of 673
ROA: none104.142.104.0/22No ROA covers it. Add a ROA for AS6561, maxLength 22.669 of 673
ROA: none104.142.111.0/24No ROA covers it. Add a ROA for AS6561, maxLength 24.669 of 673
ROA: none104.142.112.0/20No ROA covers it. Add a ROA for AS6561, maxLength 20.669 of 673
ROA: none104.163.0.0/17No ROA covers it. Add a ROA for AS6561, maxLength 17.669 of 673

Route objects not announced

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

2604:13c0::/32ARINNo 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.