bgpreport

Network · data from 2026-11-12

AS36234 COREDIAL-228 - CoreDial, LLC

Registry name: COREDIAL-228 - CoreDial, LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS36234, 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.
8.39.115.0/24 No ROA Other origin only 673 100% 67
64.94.196.0/23 No ROA Other IRR onlyRADB 672 100% 67
198.58.40.0/24 No ROA RIR databaseARIN 672 100% 67
198.58.41.0/24 No ROA RIR databaseARIN, RADB 672 100% 67
198.58.42.0/24 No ROA RIR databaseARIN, RADB 672 100% 67
198.58.43.0/24 No ROA RIR databaseARIN 672 100% 67
198.58.44.0/22 No ROA RIR databaseARIN 672 100% 67
206.166.216.0/24 No ROA RIR databaseARIN 672 100% 67
206.166.217.0/24 No ROA RIR databaseARIN, RADB 672 100% 67
206.166.218.0/23 No ROA RIR databaseARIN, RADB 672 100% 67

AS-SET

AS36234 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 23 are in fix.csv.

  • ROA: none10
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
ROA: none8.39.115.0/24No ROA covers it. Add a ROA for AS36234, maxLength 24.673 of 673
Route object: none8.39.115.0/24Route objects for it name AS36334. Add a route object with origin AS36234 in the RIR database for the space.673 of 673
ROA: none64.94.196.0/23No ROA covers it. Add a ROA for AS36234, maxLength 23.672 of 673
Route object: RIR64.94.196.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none198.58.40.0/24No ROA covers it. Add a ROA for AS36234, maxLength 24.672 of 673
ROA: none198.58.41.0/24No ROA covers it. Add a ROA for AS36234, maxLength 24.672 of 673
ROA: none198.58.42.0/24No ROA covers it. Add a ROA for AS36234, maxLength 24.672 of 673
ROA: none198.58.43.0/24No ROA covers it. Add a ROA for AS36234, maxLength 24.672 of 673
ROA: none198.58.44.0/22No ROA covers it. Add a ROA for AS36234, maxLength 22.672 of 673
ROA: none206.166.216.0/24No ROA covers it. Add a ROA for AS36234, maxLength 24.672 of 673
ROA: none206.166.217.0/24No ROA covers it. Add a ROA for AS36234, maxLength 24.672 of 673
ROA: none206.166.218.0/23No ROA covers it. Add a ROA for AS36234, maxLength 23.672 of 673

Route objects not announced

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

64.94.197.0/24RADBNo ROA
198.58.40.0/21RADBNo ROA
198.58.40.0/22ARINNo ROA
198.58.44.0/24ARIN, RADBNo ROA
198.58.45.0/24ARIN, RADBNo ROA
198.58.46.0/24ARIN, RADBNo ROA
198.58.47.0/24ARIN, RADBNo ROA
206.166.216.0/22RADBNo ROA
206.166.216.0/23ARIN, RADBNo ROA
206.166.218.0/24ARIN, RADBNo ROA
206.166.219.0/24ARIN, 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.