bgpreport

Network · data from 2026-11-12

AS212416 Proximity

Registry name: Proximity Proximity EOOD, BG · PeeringDB

6IPv4 routes 83.3% RPKI valid · 83.3% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
1RPKI invalid 1 origin · 0 maxLength
0No ROA 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS212416, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS212416, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
193.108.57.0/24 Invalid: origin Other origin only 1 0%low visibility 1
31.56.118.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
85.209.18.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
143.20.132.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
194.104.131.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
213.210.59.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
2001:67c:f18::/48 Valid RIR databaseRIPE 634 100% 68

AS-SET

AS212416's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 2 are in fix.csv.

  • ROA: origin1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: origin193.108.57.0/24ROAs covering it name AS218135, not AS212416. If AS212416 should announce it, add a ROA for AS212416.1 of 673
Route object: none193.108.57.0/24Route objects for it name AS218135. Add a route object with origin AS212416 in the RIR database for the space.1 of 673

Route objects not announced

Every route object with origin AS212416 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.