Skip to main content

AS267544

ASN267544

SIGNET INTERNET LTDA - EPP

Registry

Authoritative registration data

AS number
267544
Name
ASN267544
Organisation
SIGNET INTERNET LTDA - EPP
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

6

IPv6 prefixes

3

Total announced

9

Announced prefixes

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

Prefixes announced by AS267544
45.70.32.0/22 IPv4 /22 RPKI valid
45.71.76.0/22 IPv4 /22 not checked
45.70.32.0/23 IPv4 /23 RPKI valid
45.70.34.0/23 IPv4 /23 RPKI valid
45.71.76.0/23 IPv4 /23 not checked
45.71.78.0/23 IPv4 /23 RPKI valid
2804:4308::/32 IPv6 /32 RPKI valid
2804:4308:8000::/33 IPv6 /33 RPKI valid
2804:4308::/33 IPv6 /33 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 AS267544
Address families
IX.br (PTT.br) Rio de Janeiro: ATM/MPLA 30,000 Mbps IPv4 · IPv6
IX.br (PTT.br) São Paulo: ATM/MPLA 30,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 AS267544 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS267544 in AS paths

Observed upstreams
Families
AS268696 ASN268696 2,532 16,807
v4 v6
AS137409 GSLNETWORKS-AS-AP 16 160
v4 v6
AS61626 ASN61626 5 26
v6

No rows match “”.

Showing – of

Observed downstreams

4 networks seen after AS267544 in AS paths

Observed downstreams
Families
AS266536 ASN266536 533 6,554
v4 v6
AS264281 ASN264281 569 4,315
v4 v6
AS266497 ASN266497 515 2,122
v4 v6
AS267436 ASN267436 499 1,435
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

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