Skip to main content

AS262996

ASN262996

MEGAMINAS TELECOMUNICACOES LTDA

Registry

Authoritative registration data

AS number
262996
Name
ASN262996
Organisation
MEGAMINAS TELECOMUNICACOES LTDA
Country
Flag of Brazil BR Brazil
RIR
Registered
Source:asn:rdap retrieved

IPv4 prefixes

9

IPv6 prefixes

38

Total announced

47

Announced prefixes

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

Prefixes announced by AS262996
186.219.208.0/24 IPv4 /24 not checked
186.219.209.0/24 IPv4 /24 not checked
186.219.210.0/24 IPv4 /24 not checked
186.219.211.0/24 IPv4 /24 not checked
186.219.212.0/24 IPv4 /24 not checked
186.219.213.0/24 IPv4 /24 not checked
186.219.214.0/24 IPv4 /24 not checked
186.219.215.0/24 IPv4 /24 not checked
38.225.97.0/24 IPv4 /24 not checked
2804:9d4::/32 IPv6 /32 not checked
2804:9d4::/33 IPv6 /33 not checked
2804:9d4:8000::/34 IPv6 /34 not checked
2804:9d4::/34 IPv6 /34 not checked
2804:9d4:2000::/35 IPv6 /35 not checked
2804:9d4:8000::/35 IPv6 /35 not checked
2804:9d4::/35 IPv6 /35 not checked
2804:9d4:a000::/35 IPv6 /35 not checked
2804:9d4:c000::/35 IPv6 /35 not checked
2804:9d4:e000::/35 IPv6 /35 not checked
2804:9d4:1000::/36 IPv6 /36 not checked
2804:9d4:2000::/36 IPv6 /36 not checked
2804:9d4:3000::/36 IPv6 /36 not checked
2804:9d4:4000::/36 IPv6 /36 not checked
2804:9d4:6000::/36 IPv6 /36 not checked
2804:9d4:4200::/40 IPv6 /40 not checked
2804:9d4:4300::/40 IPv6 /40 not checked
2804:9d4:5200::/40 IPv6 /40 not checked
2804:9d4:5300::/40 IPv6 /40 not checked
2804:9d4:6000::/40 IPv6 /40 not checked
2804:9d4:6100::/40 IPv6 /40 not checked
2804:9d4:1000::/48 IPv6 /48 not checked
2804:9d4:172::/48 IPv6 /48 not checked
2804:9d4:186::/48 IPv6 /48 not checked
2804:9d4:2000::/48 IPv6 /48 not checked
2804:9d4:208::/48 IPv6 /48 not checked
2804:9d4:212::/48 IPv6 /48 not checked
2804:9d4:213::/48 IPv6 /48 not checked
2804:9d4:3000::/48 IPv6 /48 not checked
2804:9d4:4100::/48 IPv6 /48 not checked
2804:9d4:4800::/48 IPv6 /48 not checked
2804:9d4:4801::/48 IPv6 /48 not checked
2804:9d4:4900::/48 IPv6 /48 not checked
2804:9d4:4901::/48 IPv6 /48 not checked
2804:9d4:5000::/48 IPv6 /48 not checked
2804:9d4:5106::/48 IPv6 /48 not checked
2804:9d4:5107::/48 IPv6 /48 not checked
2804:9d4:5108::/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

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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 AS262996 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS262996 in AS paths

Observed upstreams
Families
AS267613 492 9,868
v4 v6
AS6939 HURRICANE 101 4,851
v6
AS266525 28 328
v4 v6
AS137409 GSLNETWORKS-AS-AP 4 187
v4 v6
AS6057 6057 5 130
v4 v6

No rows match “”.

Showing of

Observed downstreams

2 networks seen after AS262996 in AS paths

Observed downstreams
Families
AS275658 138 183
v4 v6
AS266270 ASN266270 4 4
v4

No rows match “”.

Showing of

Uncertain adjacencies

17 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS14840 ASN14840 1 180
v4 v6
AS24482 SGGS-AS-AP 2 91
v4 v6
AS51185 MAINSTREAMING-AS 2 54
v4 v6
AS22548 2 46
v4 v6
AS35280 F5 2 46
v4 v6
AS60503 2 46
v4 v6
AS36236 NETACTUATE 1 45
v4 v6
AS61573 1 45
v4 v6
AS263152 1 45
v4 v6
AS263237 1 45
v4 v6
AS28624 1 38
v6
AS52873 ASN52873 1 38
v6
AS264479 1 28
v4 v6
AS28634 ASN28634 2 16
v4
AS271253 ASN271253 2 16
v4
AS198150 SIACOM-AS 2 8
v4
AS262427 2 8
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.