TVINGO

BGP inherited

Cluster stats

Netblocks	8 · 18,424 IPv4 addresses
All fragments	9 blocks across 2 clusters
Cluster ID	209596579
Registry	RIPE
Customers	find customers using this network →

Evidence & provenance ?

Attribution	BGP parent (inherited)
Shared handles	clustered on 5 shared RIR contact/maintainer handles
Registry names	1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON

8 0 netblocks since 2026-07-05

2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
5.175.96.0/20	TVINGO	RIPE	ASSIGNED PA	● high
5.175.112.0/20	TVINGO	RIPE	ASSIGNED PA	● high
46.183.80.0/22	TVINGO	RIPE	ASSIGNED PA	● high
46.183.84.0/22	TVINGO	RIPE	ASSIGNED PA	● high
109.205.144.0/22	TVINGO	RIPE	ASSIGNED PA	● high
109.205.148.0/22	TVINGO	RIPE	ASSIGNED PA	● high
31.47.128.0/20	TVINGO	RIPE	ASSIGNED PA	● low
78.111.248.0/21	TVINGO	RIPE	ASSIGNED PA	● low

Possibly related to this organisation

what's this?

Same name family

Separately-registered clusters whose names share “TVINGO” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.

Tvingo_telekom 1 blocks

Sub-allocations under carriers

IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

Tvingo_telekom via PJSC Rostelecom sub-allocation

Network trust

what's this?

RPKI hygiene: B how networks compare →

87.5% of checked blocks have valid RPKI ROA coverage (7 of 8)

RPKI-inferred operator PJSC Rostelecom

Nearly all of this network's RPKI-covered space is cryptographically authorized for this single operator — the registered netname is likely one of its internal infrastructure labels.

No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE ROSTELECOM-MNT TOTALNET-MNT TVINGO-MNT