bgpreport

Network · data from 2026-11-12

AS53586 WITTE-1 - Wittenberg Telephone Company

Registry name: WITTE-1 - Wittenberg Telephone Company, US · not in PeeringDB

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

Announced routes

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

141.193.66.0/23 No ROA RIR databaseARIN 670 100% 68
148.59.112.0/23 No ROA RIR databaseARIN 670 100% 68
158.247.10.0/23 No ROA RIR databaseARIN 670 100% 68
199.27.196.0/22 No ROA RIR databaseARIN 670 100% 68
199.127.176.0/22 No ROA RIR databaseARIN 670 100% 68
199.168.92.0/22 No ROA RIR databaseARIN 670 100% 68
141.193.14.0/24 Valid RIR databaseARIN 670 100% 68
141.193.66.0/24 Valid RIR databaseARIN 670 100% 68
141.193.67.0/24 Valid RIR databaseARIN 670 100% 68
148.59.112.0/24 Valid RIR databaseARIN 670 100% 68
148.59.113.0/24 Valid RIR databaseARIN 670 100% 68
158.247.10.0/24 Valid RIR databaseARIN 670 100% 68
158.247.11.0/24 Valid RIR databaseARIN 670 100% 68
199.27.196.0/23 Valid RIR databaseARIN 670 100% 68
199.27.198.0/24 Valid RIR databaseARIN 670 100% 68
199.27.199.0/24 Valid RIR databaseARIN 670 100% 68
199.127.176.0/24 Valid RIR databaseARIN 670 100% 68
199.127.177.0/24 Valid RIR databaseARIN 670 100% 68
199.127.178.0/23 Valid RIR databaseARIN 670 100% 68
199.168.92.0/24 Valid RIR databaseARIN 670 100% 68
199.168.93.0/24 Valid RIR databaseARIN 670 100% 68
199.168.94.0/24 Valid RIR databaseARIN 670 100% 68
199.168.95.0/24 Valid RIR databaseARIN 670 100% 68

AS-SET

AS53586 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 11 are in fix.csv.

  • ROA: none6
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none141.193.66.0/23No ROA covers it. Add a ROA for AS53586, maxLength 23.670 of 673
ROA: none148.59.112.0/23No ROA covers it. Add a ROA for AS53586, maxLength 23.670 of 673
ROA: none158.247.10.0/23No ROA covers it. Add a ROA for AS53586, maxLength 23.670 of 673
ROA: none199.27.196.0/22No ROA covers it. Add a ROA for AS53586, maxLength 22.670 of 673
ROA: none199.127.176.0/22No ROA covers it. Add a ROA for AS53586, maxLength 22.670 of 673
ROA: none199.168.92.0/22No ROA covers it. Add a ROA for AS53586, maxLength 22.670 of 673

Route objects not announced

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

38.10.244.0/23RADBNo ROA
38.50.48.0/23RADBNo ROA
2001:470:3fa::/48ARINValid
2001:470:401::/48ARINValid
2606:5140::/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.