bgpreport

Network · data from 2026-11-12

AS62442 Dade-Samane-Fanava Dade Samane Fanava Company (PJS)

Registry name: Dade-Samane-Fanava Dade Samane Fanava Company (PJS), IR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS62442, 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.
78.157.32.0/19 Valid RIR databaseRIPE 671 100% 66
78.157.32.0/24 Valid RIR databaseRIPE 671 100% 66
78.157.34.0/24 Valid RIR databaseRIPE 671 100% 66
78.157.35.0/24 Valid RIR databaseRIPE 671 100% 66
78.157.36.0/24 Valid RIR databaseRIPE 671 100% 66
78.157.37.0/24 Valid RIR databaseRIPE 671 100% 66
78.157.38.0/24 Valid RIR databaseRIPE 671 100% 66
78.157.48.0/24 Valid RIR databaseRIPE 671 100% 66
78.157.49.0/24 Valid RIR databaseRIPE 671 100% 66
78.157.50.0/24 Valid RIR databaseRIPE 671 100% 66
78.157.51.0/24 Valid RIR databaseRIPE 671 100% 66
78.157.52.0/24 Valid RIR databaseRIPE 671 100% 66
78.157.59.0/24 Valid RIR databaseRIPE 671 100% 66
78.157.62.0/24 Valid RIR databaseRIPE 671 100% 66
78.157.63.0/24 Valid RIR databaseRIPE 671 100% 66
89.221.92.0/24 Valid RIR databaseRIPE 671 100% 66
95.38.45.0/24 Valid RIR databaseRIPE 671 100% 66
95.38.54.0/23 Valid RIR databaseRIPE 671 100% 66
185.136.133.0/24 Valid RIR databaseRIPE 671 100% 67
185.221.239.0/24 Valid RIR databaseRIPE 671 100% 66
78.157.39.0/24 Valid RIR databaseRIPE 670 100% 66
78.157.40.0/24 Valid RIR databaseRIPE 670 100% 66
78.157.41.0/24 Valid RIR databaseRIPE 670 100% 66
78.157.42.0/24 Valid RIR databaseRIPE 670 100% 66
78.157.43.0/24 Valid RIR databaseRIPE 670 100% 66
78.157.44.0/24 Valid RIR databaseRIPE 670 100% 66
78.157.45.0/24 Valid RIR databaseRIPE 670 100% 66
78.157.46.0/24 Valid RIR databaseRIPE 670 100% 67
78.157.53.0/24 Valid RIR databaseRIPE 670 100% 66
78.157.54.0/24 Valid RIR databaseRIPE 670 100% 66
78.157.56.0/24 Valid RIR databaseRIPE 670 100% 66
78.157.57.0/24 Valid RIR databaseRIPE 670 100% 66
78.157.58.0/24 Valid RIR databaseRIPE 670 100% 66
78.157.60.0/23 Valid RIR databaseRIPE 670 100% 67
78.157.47.0/24 Valid RIR databaseRIPE 669 99% 66
185.222.210.0/24 Valid RIR databaseRIPE 669 99% 67
2a04:aa01::/32 Valid RIR databaseRIPE 635 100% 67
2a10:8180::/48 Valid RIR databaseRIPE 633 100% 67
2a10:8180::/29 Valid RIR databaseRIPE 632 99% 67

AS-SET

AS62442 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 14 are in fix.csv.

  • Route object: not announced14

Route objects not announced

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

78.157.48.0/21RIPEValid
78.157.54.0/23RIPEValid
78.157.55.0/24RIPEValid
78.157.56.0/21RIPEValid
78.157.60.0/24RIPEValid
78.157.61.0/24RIPEValid
89.221.84.0/22RIPEValid
89.221.88.0/21RIPEValid
89.221.88.0/24RIPEValid
89.221.92.0/22RIPEInvalid: maxLength
89.221.93.0/24RIPEValid
95.38.41.0/24RIPEValid
95.38.43.0/24RIPEValid
95.38.58.0/24RIPEInvalid: origin

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.