bgpreport

Network · data from 2026-11-12

AS401119 MARRINERTECH - Marriner Technology Solutions

Registry name: MARRINERTECH - Marriner Technology Solutions, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS401119, 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.
2602:f8d3:22::/48 Valid Nonecovered by 2602:f8d3::/40 636 100% 68
2602:f8d3:21::/48 Valid Nonecovered by 2602:f8d3::/40 2 0%low visibility 2
23.180.24.0/24 Valid Other IRR onlyRADB 671 100% 68
2602:f8d3::/40 Valid Other IRR onlyRADB 635 100% 69

AS-SET

AS401119 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 4 are in fix.csv.

  • Route object: none2
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
Route object: none2602:f8d3:22::/48No route object for it. A route object for 2602:f8d3::/40 with origin AS401119 covers it (filters allowing more-specifics accept it). Add a route object with origin AS401119 in the RIR database for the space.636 of 636
Route object: none2602:f8d3:21::/48No route object for it. A route object for 2602:f8d3::/40 with origin AS401119 covers it (filters allowing more-specifics accept it). Add a route object with origin AS401119 in the RIR database for the space.2 of 636
Route object: RIR23.180.24.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2602:f8d3::/40Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

Every route object with origin AS401119 is announced.

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.