bgpreport

Network · data from 2026-11-12

AS1378 IBEL - Interbel Telephone Cooperative, Inc.

Registry name: IBEL - Interbel Telephone Cooperative, Inc., US · not in PeeringDB

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

Announced routes

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

38.71.48.0/20 No ROA None 673 100% 67
38.71.56.0/24 No ROA None 2 0%low visibility 2
38.44.96.0/23 No ROA Other IRR onlyRADB 670 100% 68
38.252.160.0/20 No ROA Other IRR onlyRADB 670 100% 68
65.19.234.0/23 No ROA RIR databaseARIN 670 100% 68
65.19.236.0/24 No ROA RIR databaseARIN, RADB 670 100% 68
66.113.45.0/24 No ROA RIR databaseARIN, RADB 670 100% 68
162.217.224.0/21 No ROA RIR databaseARIN, RADB 670 100% 68
162.244.172.0/22 No ROA RIR databaseARIN, RADB 670 100% 68
199.38.104.0/23 No ROA RIR databaseARIN 670 100% 68
216.146.97.0/24 No ROA RIR databaseARIN, RADB 668 99% 68

AS-SET

AS1378 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 22 are in fix.csv.

  • ROA: none11
  • Route object: none2
  • Route object: RIR2
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none38.71.48.0/20No ROA covers it. Add a ROA for AS1378, maxLength 20.673 of 673
Route object: none38.71.48.0/20No route object for it. Add a route object with origin AS1378 in the RIR database for the space.673 of 673
ROA: none38.71.56.0/24No ROA covers it. Add a ROA for AS1378, maxLength 24.2 of 673
Route object: none38.71.56.0/24No route object for it. Add a route object with origin AS1378 in the RIR database for the space.2 of 673
ROA: none38.44.96.0/23No ROA covers it. Add a ROA for AS1378, maxLength 23.670 of 673
Route object: RIR38.44.96.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.252.160.0/20No ROA covers it. Add a ROA for AS1378, maxLength 20.670 of 673
Route object: RIR38.252.160.0/20Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none65.19.234.0/23No ROA covers it. Add a ROA for AS1378, maxLength 23.670 of 673
ROA: none65.19.236.0/24No ROA covers it. Add a ROA for AS1378, maxLength 24.670 of 673
ROA: none66.113.45.0/24No ROA covers it. Add a ROA for AS1378, maxLength 24.670 of 673
ROA: none162.217.224.0/21No ROA covers it. Add a ROA for AS1378, maxLength 21.670 of 673
ROA: none162.244.172.0/22No ROA covers it. Add a ROA for AS1378, maxLength 22.670 of 673
ROA: none199.38.104.0/23No ROA covers it. Add a ROA for AS1378, maxLength 23.670 of 673
ROA: none216.146.97.0/24No ROA covers it. Add a ROA for AS1378, maxLength 24.668 of 673

Route objects not announced

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

38.44.96.0/24RADBNo ROA
38.44.97.0/24RADBNo ROA
65.19.234.0/24RADBNo ROA
65.19.235.0/24RADBNo ROA
199.38.104.0/24RADBNo ROA
199.38.105.0/24RADBNo ROA
2607:4680::/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.