Skip to main content

AS265158

ASN265158

ORBE TELECOM

Registry

Authoritative registration data

AS number
265158
Name
ASN265158
Organisation
ORBE TELECOM
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 AS265158
167.249.16.0/22 IPv4 /22 not checked
167.249.16.0/23 IPv4 /23 RPKI valid
167.249.18.0/23 IPv4 /23 RPKI valid
167.249.16.0/24 IPv4 /24 RPKI valid
167.249.17.0/24 IPv4 /24 RPKI valid
167.249.18.0/24 IPv4 /24 not checked
167.249.19.0/24 IPv4 /24 not checked
2804:2b88::/32 IPv6 /32 not checked
2804:2b88:8000::/33 IPv6 /33 RPKI valid
2804:2b88::/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 AS265158
Address families
IX.br (PTT.br) Fortaleza: ATM/MPLA 20,000 Mbps IPv4 · IPv6
IX.br (PTT.br) Rio de Janeiro: ATM/MPLA 10,000 Mbps IPv4 · IPv6
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 AS265158 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

10 networks seen before AS265158 in AS paths

Observed upstreams
Families
AS37468 ORG-AC4-AFRINIC 243 914
v4 v6
AS6939 HURRICANE 106 341
v6
AS264293 ASN264293 10 37
v4 v6
AS14840 ASN14840 2 28
v4 v6
AS6057 6057 2 20
v4 v6
AS35280 F5 6 18
v4 v6
AS137409 GSLNETWORKS-AS-AP 4 9
v4 v6
AS61626 ASN61626 1 6
v4 v6
AS7195 7195 1 3
v6
AS39120 CONVERGENZE-AS 1 3
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS265158 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.