Skip to main content

AS268068

ASN268068

TRAUDI INES SEHNEM

Registry

Authoritative registration data

AS number
268068
Name
ASN268068
Organisation
TRAUDI INES SEHNEM
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

3

Total announced

10

Announced prefixes

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

Prefixes announced by AS268068
45.168.180.0/22 IPv4 /22 not checked
45.168.180.0/23 IPv4 /23 not checked
45.168.182.0/23 IPv4 /23 not checked
45.168.180.0/24 IPv4 /24 not checked
45.168.181.0/24 IPv4 /24 not checked
45.168.182.0/24 IPv4 /24 not checked
45.168.183.0/24 IPv4 /24 not checked
2804:577c::/32 IPv6 /32 not checked
2804:577c:8000::/33 IPv6 /33 RPKI valid
2804:577c::/33 IPv6 /33 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 AS268068
Address families
IX.br (PTT.br) Porto Alegre: ATM/MPLA 10,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 AS268068 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS268068 in AS paths

Observed upstreams
Families
AS28283 ASN28283 291 976
v4 v6
AS13786 SEABORN 140 398
v4 v6
AS14840 ASN14840 3 28
v4 v6
AS6057 6057 4 16
v4 v6
AS1031 PEER1-1031 1 4
v4
AS61568 ASN61568 1 4
v4

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS268068 in AS paths

Observed downstreams
Families
AS269417 ASN269417 179 271
v4 v6
AS270811 ASN270811 37 48
v6

No rows match “”.

Showing – of

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS263152 ASN263152 1 4
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.