Network · data from 2026-11-12

AS18667 AS18667 - Web2mil S.A

Registry name: AS18667 - Web2mil S.A, UY · not in PeeringDB

3IPv4 routes 0.0% RPKI valid · 33.3% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

3No ROA 2 with no route object for this origin

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

0Route objects not announced registered with origin AS18667, seen from no peer

Announced routes

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


200.115.72.0/24	No ROA	Nonecovered by 200.115.72.0/21	670 100%	67
200.115.75.0/24	No ROA	Nonecovered by 200.115.72.0/21	670 100%	67
200.115.72.0/21	No ROA	Other IRR onlyALTDB	670 100%	67

AS-SET

AS18667 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 6 are in fix.csv.

ROA: none3
Route object: none2
Route object: RIR1

Change	Prefix or set	Detail	Full-table peers
ROA: none	200.115.72.0/24	No ROA covers it. Add a ROA for AS18667, maxLength 24.	670 of 673
Route object: none	200.115.72.0/24	No route object for it. A route object for 200.115.72.0/21 with origin AS18667 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18667 in the RIR database for the space.	670 of 673
ROA: none	200.115.75.0/24	No ROA covers it. Add a ROA for AS18667, maxLength 24.	670 of 673
Route object: none	200.115.75.0/24	No route object for it. A route object for 200.115.72.0/21 with origin AS18667 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18667 in the RIR database for the space.	670 of 673
ROA: none	200.115.72.0/21	No ROA covers it. Add a ROA for AS18667, maxLength 21.	670 of 673
Route object: RIR	200.115.72.0/21	Route object only in ALTDB. Add it in the RIR database for the space.	670 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

200.115.72.0/24

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

670 of 673

Route object: none

200.115.72.0/24

No route object for it. A route object for 200.115.72.0/21 with origin AS18667 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18667 in the RIR database for the space.

670 of 673

ROA: none

200.115.75.0/24

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

670 of 673

Route object: none

200.115.75.0/24

670 of 673

ROA: none

200.115.72.0/21

No ROA covers it. Add a ROA for AS18667, maxLength 21.

670 of 673

Route object: RIR

200.115.72.0/21

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

670 of 673

Route objects not announced

Every route object with origin AS18667 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.