Skip to main content

AS61663

ASN61663

INFOLINE BANDA LARGA

Registry

Authoritative registration data

AS number
61663
Name
ASN61663
Organisation
INFOLINE BANDA LARGA
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

3

Total announced

10

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS61663
131.100.240.0/22 IPv4 /22 not checked
170.150.252.0/22 IPv4 /22 RPKI valid
131.100.240.0/23 IPv4 /23 RPKI valid
131.100.242.0/23 IPv4 /23 RPKI valid
170.150.252.0/23 IPv4 /23 RPKI valid
170.150.254.0/23 IPv4 /23 not checked
209.14.82.0/23 IPv4 /23 RPKI not found
2804:1c94::/32 IPv6 /32 not checked
2804:1c94:8000::/33 IPv6 /33 RPKI valid
2804:1c94::/33 IPv6 /33 RPKI valid

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS61663
Address families
IX.br (PTT.br) Rio de Janeiro: ATM/MPLA 10,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS61663 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS61663 in AS paths

Observed upstreams
Families
AS263009 ASN263009 358 1,007
v4 v6
AS6939 HURRICANE 163 566
v4 v6
AS28173 ASN28173 210 274
v4
AS35280 F5 8 60
v4 v6
AS137409 GSLNETWORKS-AS-AP 9 40
v4 v6
AS6057 6057 5 18
v4 v6
AS61626 ASN61626 2 8
v4 v6
AS39120 CONVERGENZE-AS 1 7
v4 v6
AS7195 7195 1 2
v6

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS61663 in AS paths

Observed downstreams
Families
AS269273 ASN269273 268 342
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

20 adjacencies that may be an artefact of collector peering

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.