Network · data from 2026-11-12

AS271757 VIA PROVEDOR - SERVICOS MULTIMIDIA - EIRELI

Registry name: AS271757 - VIA PROVEDOR - SERVICOS MULTIMIDIA - EIRELI, BR · PeeringDB

4IPv4 routes 100.0% RPKI valid · 100.0% with a route object

4IPv6 routes 100.0% RPKI valid · 75.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

15Route objects not announced registered with origin AS271757, seen from no peer

Announced routes

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


2804:8088:ff00::/40	Valid	Nonecovered by 2804:8088:c000::/34	636 100%	67
45.185.16.0/24	Valid	Other IRR onlyRADB	671 100%	66
45.185.17.0/24	Valid	Other IRR onlyRADB	671 100%	66
45.185.18.0/24	Valid	Other IRR onlyRADB	671 100%	67
45.185.19.0/24	Valid	Other IRR onlyALTDB	669 99%	66
2804:8088:100::/40	Valid	Other IRR onlyRADB	636 100%	67
2804:8088:1000::/40	Valid	Other IRR onlyRADB	636 100%	67
2804:8088:fe00::/40	Valid	Other IRR onlyRADB	631 99%	67

AS-SET

AS271757'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 23 are in fix.csv.

Route object: none1
Route object: RIR7
Route object: not announced15

Change	Prefix or set	Detail	Full-table peers
Route object: none	2804:8088:ff00::/40	No route object for it. A route object for 2804:8088:c000::/34 with origin AS271757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271757 in the RIR database for the space.	636 of 636
Route object: RIR	45.185.16.0/24	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
Route object: RIR	45.185.17.0/24	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
Route object: RIR	45.185.18.0/24	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
Route object: RIR	45.185.19.0/24	Route object only in ALTDB. Add it in the RIR database for the space.	669 of 673
Route object: RIR	2804:8088:100::/40	Route object only in RADB. Add it in the RIR database for the space.	636 of 636
Route object: RIR	2804:8088:1000::/40	Route object only in RADB. Add it in the RIR database for the space.	636 of 636
Route object: RIR	2804:8088:fe00::/40	Route object only in RADB. Add it in the RIR database for the space.	631 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

2804:8088:ff00::/40

No route object for it. A route object for 2804:8088:c000::/34 with origin AS271757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271757 in the RIR database for the space.

636 of 636

Route object: RIR

45.185.16.0/24

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

671 of 673

Route object: RIR

45.185.17.0/24

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

671 of 673

Route object: RIR

45.185.18.0/24

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

671 of 673

Route object: RIR

45.185.19.0/24

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

669 of 673

Route object: RIR

2804:8088:100::/40

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

636 of 636

Route object: RIR

2804:8088:1000::/40

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

636 of 636

Route object: RIR

2804:8088:fe00::/40

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

631 of 636

Route objects not announced

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


2804:8088::/32	RADB	Valid
2804:8088::/34	RADB	Valid
2804:8088::/40	RADB	Valid
2804:8088:200::/40	RADB	Valid
2804:8088:300::/40	RADB	Valid
2804:8088:400::/40	RADB	Valid
2804:8088:500::/40	RADB	Valid
2804:8088:600::/40	RADB	Valid
2804:8088:700::/40	RADB	Valid
2804:8088:800::/40	RADB	Valid
2804:8088:900::/40	RADB	Valid
2804:8088:a00::/40	RADB	Valid
2804:8088:4000::/34	RADB	Valid
2804:8088:8000::/34	RADB	Valid
2804:8088:c000::/34	RADB	Valid

2804:8088::/32

RADB

Valid

2804:8088::/34

RADB

Valid

2804:8088::/40

RADB

Valid

2804:8088:200::/40

RADB

Valid

2804:8088:300::/40

RADB

Valid

2804:8088:400::/40

RADB

Valid

2804:8088:500::/40

RADB

Valid

2804:8088:600::/40

RADB

Valid

2804:8088:700::/40

RADB

Valid

2804:8088:800::/40

RADB

Valid

2804:8088:900::/40

RADB

Valid

2804:8088:a00::/40

RADB

Valid

2804:8088:4000::/34

RADB

Valid

2804:8088:8000::/34

RADB

Valid

2804:8088:c000::/34

RADB

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.