Skip to main content

AS268568

ASN268568

IMPLANTAR TELECOM SOCIEDADE LIMITADA

Registry

Authoritative registration data

AS number
268568
Name
ASN268568
Organisation
IMPLANTAR TELECOM SOCIEDADE LIMITADA
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

9

Total announced

12

Announced prefixes

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

Prefixes announced by AS268568
45.163.144.0/22 IPv4 /22 RPKI valid
45.163.144.0/23 IPv4 /23 RPKI valid
45.163.146.0/23 IPv4 /23 RPKI valid
2804:532c::/32 IPv6 /32 not checked
2804:532c:120::/45 IPv6 /45 not checked
2804:532c:128::/45 IPv6 /45 not checked
2804:532c:130::/45 IPv6 /45 RPKI valid
2804:532c:138::/45 IPv6 /45 not checked
2804:532c::/45 IPv6 /45 not checked
2804:532c:130::/46 IPv6 /46 RPKI valid
2804:532c:134::/46 IPv6 /46 not checked
2804:532c:138::/46 IPv6 /46 RPKI valid

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 AS268568
Address families
IX.br (PTT.br) São Paulo: ATM/MPLA 100,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 AS268568 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

12 networks seen before AS268568 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 1,823 5,461
v4 v6
AS3356 LEVEL3 2,478 5,188
v4 v6
AS13786 SEABORN 2,247 4,773
v4 v6
AS270735 ASN270735 1,253 2,666
v4
AS268696 ASN268696 1,023 2,105
v4 v6
AS28198 ASN28198 75 204
v4 v6
AS35280 F5 58 179
v4 v6
AS6057 6057 50 118
v4 v6
AS137409 GSLNETWORKS-AS-AP 48 107
v4 v6
AS61626 ASN61626 14 30
v4 v6
AS7195 7195 10 22
v6
AS39120 CONVERGENZE-AS 8 21
v4 v6

No rows match “”.

Showing – of

Observed downstreams

25 networks seen after AS268568 in AS paths

Observed downstreams
Families
AS268144 ASN268144 1,097 3,000
v4 v6
AS268884 ASN268884 774 2,448
v4 v6
AS268633 ASN268633 1,121 2,220
v4 v6
AS274388 ASN274388 183 1,652
v6
AS262663 ASN262663 757 1,067
v4 v6
AS273443 ASN273443 392 913
v4 v6
AS270865 ASN270865 359 912
v4 v6
AS264385 ASN264385 373 895
v4 v6
AS28572 ASN28572 467 718
v4 v6
AS270584 ASN270584 416 674
v4 v6
AS266010 ASN266010 375 655
v4 v6
AS262957 ASN262957 333 633
v4
AS272454 ASN272454 220 602
v6
AS271338 ASN271338 141 529
v4
AS270943 ASN270943 145 428
v4 v6
AS274833 ASN274833 244 333
v6
AS272218 ASN272218 244 332
v6
AS273811 ASN273811 100 317
v4
AS274672 ASN274672 179 235
v6
AS28188 ASN28188 136 174
v4
AS271034 ASN271034 55 131
v4 v6
AS268997 ASN268997 79 123
v6
AS28590 ASN28590 45 63
v4
AS273769 ASN273769 9 27
v6
AS265424 ASN265424 1 1
v4

No rows match “”.

Showing – of

Uncertain adjacencies

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