Skip to main content

AS268006

ASN268006

KRC net Telecom LTDA

Registry

Authoritative registration data

AS number
268006
Name
ASN268006
Organisation
KRC net Telecom LTDA
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

1

Total announced

5

Announced prefixes

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

Prefixes announced by AS268006
45.167.64.0/23 IPv4 /23 not checked
45.167.66.0/23 IPv4 /23 not checked
45.167.66.0/24 IPv4 /24 not checked
45.167.67.0/24 IPv4 /24 not checked
2804:5684::/32 IPv6 /32 RPKI not found

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

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS268006 in AS paths

Observed upstreams
Families
AS11432 ASN11432 549 842
v4 v6
AS6939 HURRICANE 107 243
v4 v6
AS35280 F5 7 20
v4 v6
AS137409 GSLNETWORKS-AS-AP 6 12
v4
AS6057 6057 2 8
v4 v6
AS39120 CONVERGENZE-AS 1 2
v4
AS61626 ASN61626 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS268006 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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