Skip to main content

AS265144

ASN265144

MCD INFORMATICA E TELECOMUNICACOES LTDA - ME

Registry

Authoritative registration data

AS number
265144
Name
ASN265144
Organisation
MCD INFORMATICA E TELECOMUNICACOES LTDA - ME
Country
Flag of Brazil BR Brazil
RIR
Registered
Source:asn:rdap retrieved

IPv4 prefixes

9

IPv6 prefixes

6

Total announced

15

Announced prefixes

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

Prefixes announced by AS265144
143.255.108.0/22 IPv4 /22 not checked
131.161.44.0/24 IPv4 /24 not checked
131.161.45.0/24 IPv4 /24 not checked
131.161.46.0/24 IPv4 /24 not checked
131.161.47.0/24 IPv4 /24 not checked
143.255.108.0/24 IPv4 /24 not checked
143.255.109.0/24 IPv4 /24 not checked
143.255.110.0/24 IPv4 /24 not checked
143.255.111.0/24 IPv4 /24 not checked
2804:2b44::/32 IPv6 /32 not checked
2804:2b44::/33 IPv6 /33 not checked
2804:2b44:ff00::/40 IPv6 /40 not checked
2804:2b44:ff00::/41 IPv6 /41 not checked
2804:2b44:3400::/48 IPv6 /48 not checked
2804:2b44:3464::/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 AS265144
Address families
IX.br (PTT.br) Brasília: ATM/MPLA 10,000 Mbps IPv4 · IPv6
IX.br (PTT.br) Goiânia: ATM/MPLA 10,000 Mbps IPv4 · IPv6
IX.br (PTT.br) São Paulo: ATM/MPLA 300,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 AS265144 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

23 networks seen before AS265144 in AS paths

Observed upstreams
Families
AS28329 4,812 10,906
v4 v6
AS2914 NTT-DATA-2914 1,641 5,141
v4 v6
AS52468 1,515 4,174
v4 v6
AS1031 PEER1-1031 1,613 3,743
v4 v6
AS268186 342 713
v4 v6
AS4230 ASN4230 313 394
v4 v6
AS33891 CORE-BACKBONE 150 336
v4 v6
AS3303 SWISSCOM 105 330
v4
AS52925 15 151
v4
AS268862 64 120
v6
AS6057 6057 51 118
v4 v6
AS16735 ASN16735 30 83
v4 v6
AS24961 34 81
v4
AS270460 50 64
v4 v6
AS263478 50 61
v6
AS137409 GSLNETWORKS-AS-AP 20 44
v4 v6
AS39120 14 23
v4
AS9498 BBIL-AP 3 8
v4
AS37468 ORG-AC4-AFRINIC 3 5
v6
AS53013 3 5
v4
AS7195 7195 2 2
v6
AS15830 Equinix 2 2
v4 v6
AS265192 ASN265192 1 1
v4

No rows match “”.

Showing of

Observed downstreams

23 networks seen after AS265144 in AS paths

Observed downstreams
Families
AS262531 800 4,096
v4 v6
AS270460 739 1,939
v4 v6
AS270310 938 1,636
v4 v6
AS274335 580 1,565
v4 v6
AS264919 754 1,409
v4 v6
AS267495 551 1,408
v4 v6
AS270500 543 1,406
v4 v6
AS268980 605 1,403
v4
AS269097 281 1,138
v4
AS262839 263 913
v4 v6
AS267985 272 837
v4
AS271049 536 753
v4 v6
AS266275 391 711
v4 v6
AS269405 213 627
v4 v6
AS271532 365 470
v4 v6
AS264261 244 394
v4 v6
AS263519 275 382
v4 v6
AS270888 270 354
v4 v6
AS267978 280 353
v4
AS268087 255 326
v4 v6
AS273683 150 197
v4
AS266397 98 115
v4
AS273355 34 58
v4 v6

No rows match “”.

Showing of

Uncertain adjacencies

40 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS199524 GCORE 45 173
v4 v6
AS49544 i3Dnet 28 118
v4 v6
AS24482 SGGS-AS-AP 22 114
v4 v6
AS51185 MAINSTREAMING-AS 22 96
v4 v6
AS28634 19 82
v4
AS271253 19 78
v4
AS14840 ASN14840 10 64
v4 v6
AS263152 26 63
v4 v6
AS61573 23 56
v4 v6
AS35280 F5 22 55
v4 v6
AS36236 NETACTUATE 22 54
v4 v6
AS264479 21 53
v4 v6
AS28917 19 46
v4
AS1828 UNITAS 20 44
v4
AS262427 21 43
v4
AS8455 17 39
v4
AS52873 17 37
v4 v6
AS198150 SIACOM-AS 15 35
v4
AS29049 15 34
v4
AS263237 14 21
v4 v6
AS28624 12 15
v6
AS22548 6 13
v4
AS60503 5 8
v4 v6
AS264919 2 4
v4 v6
AS270500 2 4
v4 v6
AS267495 1 4
v4 v6
AS268980 1 4
v4
AS269097 1 4
v4
AS274335 1 4
v4 v6
AS266275 2 3
v4 v6
AS267985 1 3
v4
AS263519 1 2
v4 v6
AS264261 1 2
v4 v6
AS271049 1 2
v4 v6
AS262839 1 1
v4
AS266397 1 1
v4
AS267978 1 1
v4
AS268087 1 1
v4
AS270310 1 1
v4
AS271532 1 1
v6

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.