bgpreport

Network · data from 2026-11-12

AS395502 Sunbreak Electronics

Registry name: JCOLO - JeffColo, US · PeeringDB

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

Announced routes

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

2607:9280:2::/48 No ROA Nonecovered by 2607:9280::/32 635 100% 70
2607:9280:a::/48 No ROA Nonecovered by 2607:9280::/32 635 100% 70
2607:9280:b::/48 No ROA Nonecovered by 2607:9280::/32 635 100% 70
2607:9280:1::/48 No ROA Other IRR onlyRADB 634 100% 70
23.175.0.0/24 No ROA RIR databaseARIN, RADB 671 100% 68
23.175.1.0/24 No ROA RIR databaseARIN, RADB 671 100% 68
23.171.112.0/24 No ROA RIR databaseARIN, RADB 667 99% 68

AS-SET

PeeringDB's irr_as_set for AS395502: AS395502: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 (AS395502 isn't in the set, or no route object for AS395502 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 objectsAS395502 in itNot covered
AS395502:AS-ALL ARIN 53514,609 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 12 are in fix.csv.

  • ROA: none7
  • Route object: none3
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2607:9280:2::/48No ROA covers it. Add a ROA for AS395502, maxLength 48.635 of 636
Route object: none2607:9280:2::/48No route object for it. A route object for 2607:9280::/32 with origin AS395502 covers it (filters allowing more-specifics accept it). Add a route object with origin AS395502 in the RIR database for the space.635 of 636
ROA: none2607:9280:a::/48No ROA covers it. Add a ROA for AS395502, maxLength 48.635 of 636
Route object: none2607:9280:a::/48No route object for it. A route object for 2607:9280::/32 with origin AS395502 covers it (filters allowing more-specifics accept it). Add a route object with origin AS395502 in the RIR database for the space.635 of 636
ROA: none2607:9280:b::/48No ROA covers it. Add a ROA for AS395502, maxLength 48.635 of 636
Route object: none2607:9280:b::/48No route object for it. A route object for 2607:9280::/32 with origin AS395502 covers it (filters allowing more-specifics accept it). Add a route object with origin AS395502 in the RIR database for the space.635 of 636
ROA: none2607:9280:1::/48No ROA covers it. Add a ROA for AS395502, maxLength 48.634 of 636
Route object: RIR2607:9280:1::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none23.175.0.0/24No ROA covers it. Add a ROA for AS395502, maxLength 24.671 of 673
ROA: none23.175.1.0/24No ROA covers it. Add a ROA for AS395502, maxLength 24.671 of 673
ROA: none23.171.112.0/24No ROA covers it. Add a ROA for AS395502, maxLength 24.667 of 673

Route objects not announced

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

2607:9280::/32ARIN, RADBNo 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.