bgpreport

Network · data from 2026-11-12

AS39863 Crossnet

Registry name: CROSSNET Crossnet LLC, AM · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS39863, 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.
81.89.216.0/24 Invalid: maxLength RIR databaseRIPE 90 13% 38
81.89.220.0/22 Valid Nonecovered by 81.89.208.0/20 673 100% 66
81.89.223.0/24 Valid Nonecovered by 81.89.208.0/20 672 100% 66
81.89.208.0/22 Valid RIR databaseRIPE 673 100% 66
81.89.212.0/22 Valid RIR databaseRIPE 673 100% 66
81.89.216.0/22 Valid RIR databaseRIPE 673 100% 66
81.89.209.0/24 Valid RIR databaseRIPE 672 100% 66
81.89.210.0/24 Valid RIR databaseRIPE 672 100% 66
81.89.213.0/24 Valid RIR databaseRIPE 672 100% 66
81.89.217.0/24 Valid RIR databaseRIPE 672 100% 66
81.89.218.0/24 Valid RIR databaseRIPE 672 100% 66
81.89.211.0/24 Valid RIR databaseRIPE 671 100% 66
81.89.212.0/24 Valid RIR databaseRIPE 671 100% 66
81.89.214.0/24 Valid RIR databaseRIPE 671 100% 66
81.89.215.0/24 Valid RIR databaseRIPE 671 100% 66
81.89.219.0/24 Valid RIR databaseRIPE 671 100% 66
81.89.220.0/24 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

AS39863'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.

  • ROA: maxLength1
  • Route object: none2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: maxLength81.89.216.0/24ROA 81.89.216.0/22 AS39863 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 81.89.216.0/24.90 of 673
Route object: none81.89.220.0/22No route object for it. A route object for 81.89.208.0/20 with origin AS39863 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39863 in the RIR database for the space.673 of 673
Route object: none81.89.223.0/24No route object for it. A route object for 81.89.208.0/20 with origin AS39863 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39863 in the RIR database for the space.672 of 673

Route objects not announced

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

81.89.208.0/20RIPENo ROA
81.89.208.0/24RIPEValid
81.89.222.0/24RIPEInvalid: maxLength

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.