bgpreport

Network · data from 2026-11-12

AS3261 DIPT

Registry name: DIPT-AS LLC "FTICOM", UA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS3261, 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.106.200.0/24 No ROA RIR databaseRIPE 671 100% 68
92.242.100.0/24 Valid None 10 1%low visibility 5
5.153.128.0/19 Valid None 2 0%low visibility 2
5.153.144.0/24 Valid Nonecovered by 5.153.144.0/20 2 0%low visibility 2
5.153.168.0/24 Valid Nonecovered by 5.153.168.0/22 2 0%low visibility 2
5.153.169.0/24 Valid Nonecovered by 5.153.168.0/22 2 0%low visibility 2
92.242.101.0/24 Valid None 2 0%low visibility 2
5.153.130.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
5.153.131.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
5.153.132.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
5.153.138.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
5.153.140.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
5.153.141.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
5.153.160.0/22 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS3261: RIPE::AS-DIPT. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS3261 isn't in the set, or no route object for AS3261 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS3261 in itNot covered
RIPE::AS-DIPT RIPE 7465 Yes 3

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 26 are in fix.csv.

  • ROA: none1
  • Route object: none6
  • Route object: not announced19
ChangePrefix or setDetailFull-table peers
ROA: none193.106.200.0/24No ROA covers it. Add a ROA for AS3261, maxLength 24.671 of 673
Route object: none92.242.100.0/24No route object for it. Add a route object with origin AS3261 in the RIR database for the space.10 of 673
Route object: none5.153.128.0/19No route object for it. Add a route object with origin AS3261 in the RIR database for the space.2 of 673
Route object: none5.153.144.0/24No route object for it. A route object for 5.153.144.0/20 with origin AS3261 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3261 in the RIR database for the space.2 of 673
Route object: none5.153.168.0/24No route object for it. A route object for 5.153.168.0/22 with origin AS3261 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3261 in the RIR database for the space.2 of 673
Route object: none5.153.169.0/24No route object for it. A route object for 5.153.168.0/22 with origin AS3261 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3261 in the RIR database for the space.2 of 673
Route object: none92.242.101.0/24No route object for it. Add a route object with origin AS3261 in the RIR database for the space.2 of 673

Route objects not announced

Route objects with origin AS3261 whose prefix no peer sees AS3261 announce. Many are kept on purpose (backup routes, space announced only in some places).

5.153.129.0/24RIPEValid
5.153.130.0/23RIPEValid
5.153.133.0/24RIPEValid
5.153.134.0/24RIPEValid
5.153.135.0/24RIPEValid
5.153.136.0/24RIPEValid
5.153.137.0/24RIPEValid
5.153.139.0/24RIPEValid
5.153.140.0/23RIPEValid
5.153.142.0/24RIPEValid
5.153.143.0/24RIPEValid
5.153.144.0/20RIPEValid
5.153.160.0/21RIPENo ROA
5.153.168.0/22RIPENo ROA
5.153.172.0/24RIPEInvalid: origin
5.153.173.0/24RIPEValid
5.153.174.0/24RIPEValid
5.153.175.0/24RIPENo ROA
2a02:300::/32RIPEValid

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.