bgpreport

Network · data from 2026-11-12

AS46796 SLAPPEYTEL-NET - Slappey Telephone, Inc.

Registry name: SLAPPEYTEL-NET - Slappey Telephone, Inc., US · not in PeeringDB

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

Announced routes

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

205.144.170.0/24 No ROA Other origin only 671 100% 67
209.132.198.0/24 No ROA Other origin only 671 100% 67
209.132.248.0/24 No ROA Other origin only 671 100% 67
74.113.156.0/24 No ROA RIR databaseARIN, RADB 672 100% 67
74.113.157.0/24 No ROA RIR databaseARIN, RADB 668 99% 67
74.113.158.0/24 No ROA RIR databaseARIN, RADB 668 99% 67

AS-SET

AS46796 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: none6
  • Route object: none3
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
ROA: none205.144.170.0/24No ROA covers it. Add a ROA for AS46796, maxLength 24.671 of 673
Route object: none205.144.170.0/24Route objects for it name AS7296. Add a route object with origin AS46796 in the RIR database for the space.671 of 673
ROA: none209.132.198.0/24No ROA covers it. Add a ROA for AS46796, maxLength 24.671 of 673
Route object: none209.132.198.0/24Route objects for it name AS7296. Add a route object with origin AS46796 in the RIR database for the space.671 of 673
ROA: none209.132.248.0/24No ROA covers it. Add a ROA for AS46796, maxLength 24.671 of 673
Route object: none209.132.248.0/24Route objects for it name AS7296. Add a route object with origin AS46796 in the RIR database for the space.671 of 673
ROA: none74.113.156.0/24No ROA covers it. Add a ROA for AS46796, maxLength 24.672 of 673
ROA: none74.113.157.0/24No ROA covers it. Add a ROA for AS46796, maxLength 24.668 of 673
ROA: none74.113.158.0/24No ROA covers it. Add a ROA for AS46796, maxLength 24.668 of 673

Route objects not announced

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

8.15.152.0/22RADBNo ROA
8.35.84.0/22RADBNo ROA
74.113.156.0/22RADBNo ROA
74.113.156.0/23RADBNo ROA
74.113.158.0/23RADBNo ROA
74.113.159.0/24ARIN, RADBNo ROA
148.78.245.0/24RADBNo ROA
164.153.0.0/19RADBNo ROA
173.227.128.0/22RADBNo ROA
204.9.187.0/24RADBNo ROA
209.114.192.0/19RADBNo ROA
209.114.215.0/24RADBNo ROA
209.151.192.0/19RADBNo ROA
216.213.96.0/20RADBNo 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.