Skip to main content

AS61624

ASN61624

INFNOC TECNOLOGIA LTDA

Registry

Authoritative registration data

AS number
61624
Name
ASN61624
Organisation
INFNOC TECNOLOGIA LTDA
Country
Flag of Brazil BR Brazil
RIR
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

4

Total announced

5

Announced prefixes

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

Prefixes announced by AS61624
151.242.95.0/24 IPv4 /24 not checked
2804:945c::/32 IPv6 /32 not checked
2804:945c:1000::/48 IPv6 /48 not checked
2804:945c:12::/48 IPv6 /48 not checked
2804:945c:6::/48 IPv6 /48 not checked

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 AS61624
Address families
AMS-IX 250 Mbps IPv4 · IPv6
DE-CIX New York: DE-CIX New York Peering LAN 20,000 Mbps IPv4 · IPv6
IX.br (PTT.br) Brasília: ATM/MPLA 10,000 Mbps IPv4 · IPv6
IX.br (PTT.br) Curitiba: ATM/MPLA 10,000 Mbps IPv4 · IPv6
IX.br (PTT.br) Fortaleza: ATM/MPLA 20,000 Mbps IPv4 · IPv6
IX.br (PTT.br) Porto Alegre: ATM/MPLA 10,000 Mbps IPv4 · IPv6
IX.br (PTT.br) São Paulo: ATM/MPLA 100,000 Mbps IPv4 · IPv6
PIT Paraguay 20,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 AS61624 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS61624 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 4,621 9,743
v4 v6
AS3356 LEVEL3 1,386 2,400
v4 v6
AS52925 27 170
v4 v6
AS37468 ORG-AC4-AFRINIC 50 156
v4
AS7195 7195 7 16
v6
AS137409 GSLNETWORKS-AS-AP 10 14
v4
AS6057 6057 4 12
v4 v6
AS61512 3 3
v4

No rows match “”.

Showing of

Observed downstreams

9 networks seen after AS61624 in AS paths

Observed downstreams
Families
AS269783 3,177 5,483
v4 v6
AS270052 630 1,313
v4 v6
AS272065 274 1,002
v4 v6
AS273847 274 991
v4 v6
AS266400 551 765
v4 v6
AS272026 274 666
v4 v6
AS274041 302 421
v4 v6
AS264092 257 334
v4
AS20940 AKAMAI-ASN1 3 3
v4

No rows match “”.

Showing of

Uncertain adjacencies

21 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS60503 36 75
v4 v6
AS53046 8 24
v4 v6
AS24482 SGGS-AS-AP 4 20
v4 v6
AS51185 MAINSTREAMING-AS 4 16
v4 v6
AS28634 ASN28634 4 12
v4
AS22548 4 10
v4 v6
AS35280 F5 4 10
v4 v6
AS36236 NETACTUATE 4 10
v4 v6
AS52873 ASN52873 4 10
v4 v6
AS61573 4 10
v4 v6
AS263152 4 10
v4 v6
AS263237 4 10
v4 v6
AS264479 4 7
v4 v6
AS37721 ORG-VTS1-AFRINIC 4 6
v4
AS262427 4 6
v4
AS199524 GCORE 2 6
v4 v6
AS269783 2 4
v4
AS271253 ASN271253 2 4
v4
AS28624 1 4
v6
AS198150 SIACOM-AS 2 2
v4
AS264092 1 1
v4

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.