Skip to main content

AS219310

R09TELECOM

R09-TELECOM

Registry

Authoritative registration data

AS number
219310
Name
R09TELECOM
Organisation
R09-TELECOM
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

0

IPv6 prefixes

8

Total announced

8

Announced prefixes

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

Prefixes announced by AS219310
2a0b:4e07:280::/48 IPv6 /48 not checked
2a0b:4e07:281::/48 IPv6 /48 not checked
2a0b:4e07:282::/48 IPv6 /48 not checked
2a0b:4e07:285::/48 IPv6 /48 not checked
2a0b:4e07:287::/48 IPv6 /48 not checked
2a0b:4e07:288::/48 IPv6 /48 not checked
2a0b:4e07:28a::/48 IPv6 /48 not checked
2a0b:4e07:28f::/48 IPv6 /48 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 AS219310
Address families
EVIX: Peering LAN 1,000 Mbps 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 AS219310 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS219310 in AS paths

Observed upstreams
Families
AS212895 ROUTE64_ORG 235 1,165
v6
AS197324 Vladyslav 236 592
v6
AS47272 HYEHOST 221 291
v6
AS218569 PODRIL1AK2-AS 216 291
v6
AS211509 RUDAKI-AS 2 12
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS219310 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS37989 DCS1PTELTD-AS-AP 1 6
v6
AS58057 SECUREBIT 1 6
v6

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.