Skip to main content

AS51675

WEBDEV-AS

WEBDEV Sp. z o.o.

Registry

Authoritative registration data

AS number
51675
Name
WEBDEV-AS
Organisation
WEBDEV Sp. z o.o.
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

1

Total announced

4

Announced prefixes

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

Prefixes announced by AS51675
46.17.112.0/21 IPv4 /21 not checked
46.17.112.0/22 IPv4 /22 not checked
46.17.116.0/22 IPv4 /22 not checked
2a02:2680::/32 IPv6 /32 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 AS51675
Address families
TPIX PL 5,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 AS51675 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS51675 in AS paths

Observed upstreams
Families
AS29535 MIX2_OpenPeering 359 1,371
v4
AS20804 ASN-TELENERGO 328 1,147
v4 v6
AS6939 HURRICANE 62 82
v6
AS58307 RIX 19 22
v6
AS6204 ZET-NET 2 6
v4

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS51675 in AS paths

Observed downstreams
Families
AS34402 INFOPLUS-AS 299 1,152
v4

No rows match “”.

Showing – of

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 2 14
v4 v6
AS28917 Fiord-AS 2 8
v4 v6
AS24482 SGGS-AS-AP 2 7
v4 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.