Network · data from 2026-11-12

AS61663 INFOLINE BANDA LARGA LTDA

Registry name: AS61663 - INFOLINE BANDA LARGA, BR · PeeringDB

7IPv4 routes 85.7% 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

1No ROA 2 with no route object for this origin

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

8Route objects not announced registered with origin AS61663, seen from no peer

Announced routes

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


209.14.82.0/23	No ROA	Other IRR onlyRADB	208 31%	56
2804:1c94::/33	Valid	Nonecovered by 2804:1c94::/32	353 56%	65
2804:1c94:8000::/33	Valid	Nonecovered by 2804:1c94::/32	352 55%	65
131.100.240.0/22	Valid	Other IRR onlyRADB, TC	670 100%	67
170.150.252.0/22	Valid	Other IRR onlyRADB, TC	670 100%	67
2804:1c94::/32	Valid	Other IRR onlyRADB, TC	635 100%	67
131.100.240.0/23	Valid	Other IRR onlyRADB	206 31%	56
131.100.242.0/23	Valid	Other IRR onlyRADB	206 31%	56
170.150.252.0/23	Valid	Other IRR onlyRADB	206 31%	56
170.150.254.0/23	Valid	Other IRR onlyRADB	206 31%	56

AS-SET

AS61663'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 19 are in fix.csv.

ROA: none1
Route object: none2
Route object: RIR8
Route object: not announced8

Change	Prefix or set	Detail	Full-table peers
ROA: none	209.14.82.0/23	No ROA covers it. Add a ROA for AS61663, maxLength 23.	208 of 673
Route object: RIR	209.14.82.0/23	Route object only in RADB. Add it in the RIR database for the space.	208 of 673
Route object: none	2804:1c94::/33	No route object for it. A route object for 2804:1c94::/32 with origin AS61663 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61663 in the RIR database for the space.	353 of 636
Route object: none	2804:1c94:8000::/33	No route object for it. A route object for 2804:1c94::/32 with origin AS61663 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61663 in the RIR database for the space.	352 of 636
Route object: RIR	131.100.240.0/22	Route object only in RADB, TC. Add it in the RIR database for the space.	670 of 673
Route object: RIR	170.150.252.0/22	Route object only in RADB, TC. Add it in the RIR database for the space.	670 of 673
Route object: RIR	2804:1c94::/32	Route object only in RADB, TC. Add it in the RIR database for the space.	635 of 636
Route object: RIR	131.100.240.0/23	Route object only in RADB. Add it in the RIR database for the space.	206 of 673
Route object: RIR	131.100.242.0/23	Route object only in RADB. Add it in the RIR database for the space.	206 of 673
Route object: RIR	170.150.252.0/23	Route object only in RADB. Add it in the RIR database for the space.	206 of 673
Route object: RIR	170.150.254.0/23	Route object only in RADB. Add it in the RIR database for the space.	206 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

209.14.82.0/23

No ROA covers it. Add a ROA for AS61663, maxLength 23.

208 of 673

Route object: RIR

209.14.82.0/23

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

208 of 673

Route object: none

2804:1c94::/33

No route object for it. A route object for 2804:1c94::/32 with origin AS61663 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61663 in the RIR database for the space.

353 of 636

Route object: none

2804:1c94:8000::/33

352 of 636

Route object: RIR

131.100.240.0/22

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

670 of 673

Route object: RIR

170.150.252.0/22

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

670 of 673

Route object: RIR

2804:1c94::/32

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

635 of 636

Route object: RIR

131.100.240.0/23

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

206 of 673

Route object: RIR

131.100.242.0/23

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

206 of 673

Route object: RIR

170.150.252.0/23

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

206 of 673

Route object: RIR

170.150.254.0/23

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

206 of 673

Route objects not announced

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


131.100.240.0/24	RADB	Valid
131.100.241.0/24	RADB	Valid
131.100.242.0/24	RADB	Valid
131.100.243.0/24	RADB	Valid
170.150.252.0/24	RADB	Valid
170.150.253.0/24	RADB	Valid
170.150.254.0/24	RADB	Valid
170.150.255.0/24	RADB	Valid

131.100.240.0/24

RADB

Valid

131.100.241.0/24

RADB

Valid

131.100.242.0/24

RADB

Valid

131.100.243.0/24

RADB

Valid

170.150.252.0/24

RADB

Valid

170.150.253.0/24

RADB

Valid

170.150.254.0/24

RADB

Valid

170.150.255.0/24

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.