Network · data from 2026-11-12

AS7057 MNSI Telecom

Registry name: MANAGEDNETWORK - Managed Network Systems Inc., CA · PeeringDB

10IPv4 routes 90.0% RPKI valid · 100.0% with a route object

1IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

1No ROA 0 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

1Route objects not announced registered with origin AS7057, seen from no peer

Announced routes

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


204.187.59.0/24	No ROA	Other IRR onlyRADB	671 100%	68
216.8.128.0/19	Valid	Other IRR onlyRADB	671 100%	68
216.8.160.0/19	Valid	Other IRR onlyRADB	671 100%	68
15.195.0.0/16	Valid	RIR databaseARIN	671 100%	68
15.208.0.0/16	Valid	RIR databaseARIN	671 100%	68
98.143.64.0/20	Valid	RIR databaseARIN, RADB	671 100%	68
104.254.8.0/22	Valid	RIR databaseARIN, RADB	671 100%	68
216.8.128.0/18	Valid	RIR databaseARIN, RADB	671 100%	68
216.174.64.0/18	Valid	RIR databaseARIN, RADB	671 100%	68
216.252.208.0/22	Valid	RIR databaseARIN, RADB	671 100%	68
2600:dc00::/28	Valid	RIR databaseARIN, RADB	634 100%	70

AS-SET

PeeringDB's irr_as_set for AS7057: RADB::AS-MNSI. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS7057 isn't in the set, or no route object for AS7057 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

Name	Database	ASNs	Sets	Route objects	AS7057 in it	Not covered
RADB::AS-MNSI	RADB	9	1	65	Yes	0

Name

Database

ASNs

Sets

Route objects

AS7057 in it

Not covered

RADB::AS-MNSI

RADB

Yes

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.

ROA: none1
Route object: RIR3
Route object: not announced1

Change	Prefix or set	Detail	Full-table peers
ROA: none	204.187.59.0/24	No ROA covers it. Add a ROA for AS7057, maxLength 24.	671 of 673
Route object: RIR	204.187.59.0/24	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
Route object: RIR	216.8.128.0/19	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
Route object: RIR	216.8.160.0/19	Route object only in RADB. Add it in the RIR database for the space.	671 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

204.187.59.0/24

No ROA covers it. Add a ROA for AS7057, maxLength 24.

671 of 673

Route object: RIR

204.187.59.0/24

Route object only in RADB. Add it in the RIR database for the space.

671 of 673

Route object: RIR

216.8.128.0/19

Route object only in RADB. Add it in the RIR database for the space.

671 of 673

Route object: RIR

216.8.160.0/19

Route object only in RADB. Add it in the RIR database for the space.

671 of 673

Route objects not announced

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


216.8.176.0/22	ARIN	Valid

216.8.176.0/22

ARIN

Valid

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.