Skip to main content

AS61917

ASN61917

NETMAIS TELECOM

Registry

Authoritative registration data

AS number
61917
Name
ASN61917
Organisation
NETMAIS TELECOM
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

21

IPv6 prefixes

6

Total announced

27

Announced prefixes

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

Prefixes announced by AS61917
167.250.56.0/22 IPv4 /22 not checked
179.124.132.0/22 IPv4 /22 RPKI valid
45.188.152.0/22 IPv4 /22 RPKI valid
167.250.56.0/23 IPv4 /23 not checked
167.250.58.0/23 IPv4 /23 not checked
179.124.132.0/23 IPv4 /23 not checked
179.124.134.0/23 IPv4 /23 not checked
45.188.152.0/23 IPv4 /23 not checked
45.188.154.0/23 IPv4 /23 not checked
167.250.56.0/24 IPv4 /24 RPKI valid
167.250.57.0/24 IPv4 /24 RPKI valid
167.250.58.0/24 IPv4 /24 not checked
167.250.59.0/24 IPv4 /24 RPKI valid
179.124.132.0/24 IPv4 /24 RPKI valid
179.124.133.0/24 IPv4 /24 not checked
179.124.134.0/24 IPv4 /24 not checked
179.124.135.0/24 IPv4 /24 RPKI valid
45.188.152.0/24 IPv4 /24 not checked
45.188.153.0/24 IPv4 /24 RPKI valid
45.188.154.0/24 IPv4 /24 not checked
45.188.155.0/24 IPv4 /24 not checked
2804:16cc::/32 IPv6 /32 not checked
2804:16cc:8000::/33 IPv6 /33 RPKI valid
2804:16cc::/33 IPv6 /33 RPKI valid
2804:16cc:1000::/36 IPv6 /36 RPKI valid
2804:16cc:2000::/36 IPv6 /36 RPKI valid
2804:16cc::/36 IPv6 /36 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 AS61917
Address families
IX.br (PTT.br) Fortaleza: ATM/MPLA 20,000 Mbps IPv4 · IPv6
IX.br (PTT.br) Palmas 10,000 Mbps IPv4 · IPv6
IX.br (PTT.br) São Paulo: ATM/MPLA 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 AS61917 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS61917 in AS paths

Observed upstreams
Families
AS61832 ASN61832 2,137 7,008
v4 v6
AS267613 ASN267613 2,270 6,818
v4 v6
AS137409 GSLNETWORKS-AS-AP 41 319
v4 v6
AS35280 F5 20 242
v4 v6
AS6057 6057 28 148
v4 v6
AS61626 ASN61626 1 22
v4 v6
AS39120 CONVERGENZE-AS 1 16
v4 v6
AS28368 ASN28368 6 6
v6
AS7195 7195 1 5
v6

No rows match “”.

Showing – of

Observed downstreams

13 networks seen after AS61917 in AS paths

Observed downstreams
Families
AS266614 ASN266614 533 3,183
v4 v6
AS262452 ASN262452 796 2,910
v4 v6
AS268092 ASN268092 275 1,536
v4 v6
AS264591 ASN264591 359 786
v4 v6
AS272453 ASN272453 249 670
v6
AS266355 ASN266355 255 597
v4 v6
AS273774 ASN273774 380 500
v4 v6
AS52747 ASN52747 299 464
v4 v6
AS263069 ASN263069 281 370
v4 v6
AS275615 ASN275615 251 334
v6
AS269038 ASN269038 22 26
v4
AS265101 ASN265101 20 25
v4
AS262663 ASN262663 14 18
v4

No rows match “”.

Showing – of

Uncertain adjacencies

26 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.