Skip to main content

AS274366

ASN274366

Royal Company Infinity LTDA

Registry

Authoritative registration data

AS number
274366
Name
ASN274366
Organisation
Royal Company Infinity LTDA
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

4

Total announced

9

Announced prefixes

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

Prefixes announced by AS274366
190.11.212.0/23 IPv4 /23 not checked
190.11.212.0/24 IPv4 /24 not checked
190.11.213.0/24 IPv4 /24 not checked
190.11.214.0/24 IPv4 /24 not checked
190.11.215.0/24 IPv4 /24 not checked
2804:96e4::/32 IPv6 /32 RPKI valid
2804:96e4::/33 IPv6 /33 RPKI valid
2804:96e4:4000::/34 IPv6 /34 RPKI valid
2804:96e4::/34 IPv6 /34 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 AS274366
Address families
IX.br (PTT.br) São Paulo: ATM/MPLA 20,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 AS274366 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

10 networks seen before AS274366 in AS paths

Observed upstreams
Families
AS3356 LEVEL3 207 430
v4 v6
AS6939 HURRICANE 63 188
v4 v6
AS272658 ASN272658 150 175
v4
AS52468 52468 114 132
v4
AS273478 ASN273478 33 80
v6
AS35280 F5 3 19
v4 v6
AS6057 6057 3 12
v4 v6
AS53013 ASN53013 3 5
v4
AS61626 ASN61626 1 4
v4 v6
AS7195 7195 1 2
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS274366 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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