Skip to main content

AS264556

ASN264556

GARCIA TELECOMUNICACOES LTDA

Registry

Authoritative registration data

AS number
264556
Name
ASN264556
Organisation
GARCIA TELECOMUNICACOES LTDA
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

10

IPv6 prefixes

7

Total announced

17

Announced prefixes

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

Prefixes announced by AS264556
138.0.206.0/23 IPv4 /23 RPKI valid
168.227.88.0/23 IPv4 /23 not checked
138.0.204.0/24 IPv4 /24 not checked
138.0.205.0/24 IPv4 /24 not checked
138.0.206.0/24 IPv4 /24 not checked
138.0.207.0/24 IPv4 /24 not checked
168.227.88.0/24 IPv4 /24 not checked
168.227.89.0/24 IPv4 /24 not checked
168.227.90.0/24 IPv4 /24 not checked
168.227.91.0/24 IPv4 /24 RPKI valid
2804:2178::/32 IPv6 /32 RPKI valid
2804:2178:5000::/36 IPv6 /36 RPKI valid
2804:2178:4001::/48 IPv6 /48 RPKI valid
2804:2178:4002::/48 IPv6 /48 RPKI valid
2804:2178:4004::/48 IPv6 /48 RPKI valid
2804:2178:4fff::/48 IPv6 /48 RPKI valid
2804:2178:5000::/48 IPv6 /48 RPKI valid

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

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS264556 in AS paths

Observed upstreams
Families
AS271253 ASN271253 9,599 35,334
v4 v6
AS1031 PEER1-1031 906 3,448
v4
AS16265 LEASEWEB-NETWORK 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

22 networks seen after AS264556 in AS paths

Observed downstreams
Families
AS264880 ASN264880 3,119 9,100
v4 v6
AS265466 ASN265466 439 3,722
v4 v6
AS265321 ASN265321 469 3,696
v4 v6
AS262395 ASN262395 440 2,712
v4 v6
AS270322 ASN270322 446 2,037
v4 v6
AS266141 ASN266141 481 1,747
v4
AS267074 ASN267074 556 1,356
v4
AS266119 ASN266119 421 1,337
v4 v6
AS266047 ASN266047 427 1,331
v4 v6
AS272171 ASN272171 258 1,008
v6
AS272434 ASN272434 245 996
v6
AS269181 ASN269181 445 922
v4 v6
AS269295 ASN269295 207 741
v4 v6
AS273739 ASN273739 255 668
v6
AS266366 ASN266366 128 390
v4 v6
AS267232 ASN267232 275 339
v4
AS270601 ASN270601 271 338
v4
AS270843 ASN270843 257 336
v6
AS267038 ASN267038 227 297
v4
AS268494 ASN268494 78 221
v4
AS268690 ASN268690 138 178
v4 v6
AS269675 ASN269675 144 174
v4

No rows match “”.

Showing – of

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS199524 GCORE 27 78
v4
AS49544 i3Dnet 1 12
v4 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.