bgpreport

Network · data from 2026-11-12

AS395649 Schwartz Networks AS395649

Registry name: SCHWARTZNET-B - Schwartz Networks Limited Liability Company, US · PeeringDB

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

Announced routes

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

2604:7c40:1::/48 Valid Other origin onlycovered by 2604:7c40::/36 634 100% 69

AS-SET

AS395649's PeeringDB record names no 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 6 are in fix.csv.

  • Route object: none1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
Route object: none2604:7c40:1::/48Route objects for it name AS31867. A route object for 2604:7c40::/36 with origin AS395649 covers it (filters allowing more-specifics accept it). Add a route object with origin AS395649 in the RIR database for the space.634 of 636

Route objects not announced

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

23.149.192.0/24ARINInvalid: origin
74.113.97.0/24ARINValid
162.213.130.0/24ARINInvalid: origin
2602:fd6f:e::/48ARIN, RADBValid
2604:7c40::/36ARIN, RADBValid

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.