RFC Internet Sp. z o.o.
Data as of 2026-08-16
BGP inherited
Cluster stats
| Netblocks | 31 · 17,161 IPv4 addresses |
| IPv6 | 7 prefixes (largest 2a12:6cc0::/29) |
| Cluster ID | 222375967 |
| Registry | BGP |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 10 shared RIR contact/maintainer handles |
| Registry names | 4 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
Footprint over time
8 weekly snapshots · JSON
33
-2 netblocks since 2026-07-05
2026-07-05
peak 35
2026-08-16
IP Ranges (31)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 46.238.212.0/22 | RFC Internet Sp. z o.o. | BGP | ANNOUNCED | ● high |
| 46.238.228.0/22 | RFC Internet Sp. z o.o. | BGP | ANNOUNCED | ● high |
| 46.238.236.0/22 | RFC Internet Sp. z o.o. | BGP | ANNOUNCED | ● high |
| 46.238.240.0/21 | RFC Internet Sp. z o.o. | BGP | ANNOUNCED | ● high |
| 46.238.248.0/23 | RFC Internet Sp. z o.o. | BGP | ANNOUNCED | ● high |
| 46.239.176.0/20 | RFC Internet Sp. z o.o. | BGP | ANNOUNCED | ● high |
| 89.46.145.7/32 | RFC Internet | PEERINGDB | ASSIGNED | ● high |
| 89.191.152.0/23 | RFC Internet Sp. z o.o. | BGP | ANNOUNCED | ● high |
| 89.191.154.0/24 | RFC Internet Sp. z o.o. | BGP | ANNOUNCED | ● high |
| 94.101.16.0/20 | RFC Internet Sp. z o.o. | BGP | ANNOUNCED | ● high |
| 94.141.135.0/24 | RFC Internet Sp. z o.o. | BGP | ANNOUNCED | ● high |
| 94.141.152.0/23 | RFC Internet Sp. z o.o. | BGP | ANNOUNCED | ● high |
| 178.216.42.63/32 | RFC Internet | PEERINGDB | ASSIGNED | ● high |
| 185.174.152.0/23 | RFC Internet Sp. z o.o. | BGP | ANNOUNCED | ● high |
| 185.179.57.0/24 | RFC Internet Sp. z o.o. | BGP | ANNOUNCED | ● high |
| 193.104.229.0/24 | RFC Internet Sp. z o.o. | BGP | ANNOUNCED | ● high |
| 195.149.233.127/32 | RFC Internet | PEERINGDB | ASSIGNED | ● high |
| 195.149.233.159/32 | RFC Internet | PEERINGDB | ASSIGNED | ● high |
| 195.191.170.6/32 | RFC Internet | PEERINGDB | ASSIGNED | ● high |
| 2001:678:3ac::649/128 | RFC Internet | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:27::4:8789:1/128 | RFC Internet | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:27::4:8789:2/128 | RFC Internet | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:5b::613/128 | RFC Internet | PEERINGDB | ASSIGNED | ● high |
| 2a10:f780::6/128 | RFC Internet | PEERINGDB | ASSIGNED | ● high |
| 2a12:6cc0::/32 | RFC Internet Sp. z o.o. | BGP | ANNOUNCED | ● high |
| 2.57.8.0/24 | RFC Internet Sp. z o.o. | RIPE | ASSIGNED PA | ● low |
| 2.57.8.0/23 | RFC Internet Sp. z o.o. | RIPE | ALLOCATED PA | ● low |
| 2.57.9.0/24 | RFC Internet Sp. z o.o. | RIPE | ASSIGNED PA | ● low |
| 185.179.56.0/23 | RFC Internet Sp. z o.o. | RIPE | ALLOCATED PA | ● low |
| 195.116.66.16/30 | RFC-INTERNET | RIPE | ASSIGNED PA | ● low |
| 2a12:6cc0::/29 | RFC Internet Sp. z o.o. | RIPE | ALLOCATED-BY-RIR | ● low |
IPv6 ranges (7)
Network trust
what's this?
RPKI hygiene: C
how networks compare →
78.8%
of checked blocks have valid RPKI ROA coverage
(26 of 33)
Possible discrepancies (1)
These blocks are registered to RFC Internet Sp. z o.o. but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 46.238.228.0/22 /22 | authorized for AS12618 — Politechnika Bydgoska im. Jana i Jedrzeja Sniadeckich |
NIC Handles
AS48789
AS48789
DUMY-RIPE
DUMY-RIPE
ORG-RISZ3-RIPE
PL-BYDMAN-MNT
RFC-MNT
RFC-MNT
RIPE-NCC-HM-MNT
TPNET