Skip to main content

AS39612

TEVIA-AS

************************************

Registry

Authoritative registration data

AS number
39612
Name
TEVIA-AS
Organisation
************************************
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

13

IPv6 prefixes

0

Total announced

13

Announced prefixes

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

Prefixes announced by AS39612
80.248.48.0/23 IPv4 /23 not checked
80.248.52.0/23 IPv4 /23 not checked
80.248.50.0/24 IPv4 /24 not checked
80.248.51.0/24 IPv4 /24 not checked
80.248.54.0/24 IPv4 /24 not checked
80.248.55.0/24 IPv4 /24 not checked
80.248.56.0/24 IPv4 /24 not checked
80.248.57.0/24 IPv4 /24 not checked
80.248.58.0/24 IPv4 /24 not checked
80.248.59.0/24 IPv4 /24 not checked
80.248.61.0/24 IPv4 /24 not checked
80.248.62.0/24 IPv4 /24 not checked
80.248.63.0/24 IPv4 /24 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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 AS39612 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS39612 in AS paths

Observed upstreams
Families
AS35598 INETCOM 210 2,057
v4
AS57304 RETNRU-AS 81 1,170
v4
AS3216 SOVAM-AS 67 902
v4
AS62255 BEMYLINK 11 122
v4
AS41327 FIBERTELECOM-AS 3 15
v4

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS39612 in AS paths

Observed downstreams
Families
AS203974 GPM-KIT 85 101
v4
AS51532 TEVIA-AS 26 32
v4

No rows match “”.

Showing – of

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 2 14
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.