bgpreport

Network · data from 2026-11-12

AS210434 nets360

Registry name: AS-NETS360 nets360 OU, EE · PeeringDB

1IPv4 routes 100.0% RPKI valid · 0.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.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
4Route objects not announced registered with origin AS210434, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS210434, 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.
193.138.27.0/24 Valid Other origin only 655 97% 66
2001:67c:16cc::/48 Valid RIR databaseRIPE 634 100% 69

AS-SET

AS210434'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 5 are in fix.csv.

  • Route object: none1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: none193.138.27.0/24Route objects for it name AS12337. Add a route object with origin AS210434 in the RIR database for the space.655 of 673

Route objects not announced

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

2a12:4e80::/29ALTDB, RADBNo ROA
2a12:e940::/29ALTDBInvalid: origin
2a12:f240::/29ALTDB, RADBNo ROA
2a12:f4c0::/29ALTDB, RADBNo 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.