bgpreport

Network · data from 2026-11-12

AS200260 Debugged-Network

Registry name: Debugged-Network Debugged Ltd, GB · PeeringDB

36IPv4 routes 69.4% RPKI valid · 25.0% with a route object
2IPv6 routes 100.0% RPKI valid · 100.0% with a route object
9RPKI invalid 9 origin · 0 maxLength
2No ROA 27 with no route object for this origin
11Low visibility seen by under 10% of full-table peers
5Route objects not announced registered with origin AS200260, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS200260, 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.

51.241.44.0/24 Invalid: origin Other origin only 2 0%low visibility 2
51.241.45.0/24 Invalid: origin Other origin only 2 0%low visibility 2
51.241.46.0/24 Invalid: origin Other origin only 2 0%low visibility 2
82.29.8.0/22 Invalid: origin Other origin only 2 0%low visibility 2
82.29.8.0/24 Invalid: origin None 2 0%low visibility 2
82.29.9.0/24 Invalid: origin None 2 0%low visibility 2
82.29.10.0/24 Invalid: origin None 2 0%low visibility 2
82.29.11.0/24 Invalid: origin None 2 0%low visibility 2
51.241.50.0/24 Invalid: origin Other origin only 1 0%low visibility 1
51.241.44.0/22 No ROA None 2 0%low visibility 2
51.241.48.0/22 No ROA None 2 0%low visibility 2
82.29.12.0/24 Valid Nonecovered by 82.29.12.0/22 672 100% 67
82.29.13.0/24 Valid Nonecovered by 82.29.12.0/22 672 100% 67
82.29.14.0/24 Valid Nonecovered by 82.29.12.0/22 672 100% 67
82.29.15.0/24 Valid Nonecovered by 82.29.12.0/22 672 100% 67
82.39.200.0/24 Valid Nonecovered by 82.39.200.0/22 672 100% 67
82.39.201.0/24 Valid Nonecovered by 82.39.200.0/22 672 100% 67
82.39.202.0/24 Valid Nonecovered by 82.39.200.0/22 672 100% 67
82.39.203.0/24 Valid Nonecovered by 82.39.200.0/22 672 100% 67
82.110.132.0/24 Valid Nonecovered by 82.110.132.0/22 672 100% 67
82.110.133.0/24 Valid Nonecovered by 82.110.132.0/22 672 100% 67
82.110.134.0/24 Valid Nonecovered by 82.110.132.0/22 672 100% 67
82.110.135.0/24 Valid Nonecovered by 82.110.132.0/22 672 100% 67
206.208.120.0/24 Valid Nonecovered by 206.208.120.0/22 672 100% 67
206.208.121.0/24 Valid Nonecovered by 206.208.120.0/22 672 100% 67
206.208.122.0/24 Valid Nonecovered by 206.208.120.0/22 672 100% 67
206.208.123.0/24 Valid Nonecovered by 206.208.120.0/22 672 100% 67
82.110.132.0/22 Valid Other IRR onlyRADB 672 100% 67
31.42.122.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
62.84.167.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
82.29.12.0/22 Valid RIR databaseRADB, RIPE 672 100% 67
82.39.200.0/22 Valid RIR databaseRADB, RIPE 672 100% 67
109.110.163.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
193.242.222.0/24 Valid RIR databaseRIPE 672 100% 67
206.208.120.0/22 Valid RIR databaseARIN 672 100% 67
45.92.41.0/24 Valid RIR databaseRIPE 671 100% 67
2a13:75c1:500::/40 Valid RIR databaseRIPE 634 100% 69
2a13:75c1:2000::/36 Valid RIR databaseRIPE 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS200260: AS200260:AS-DEBUGGED. 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 (AS200260 isn't in the set, or no route object for AS200260 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 objectsAS200260 in itNot covered
AS200260:AS-DEBUGGED RIPE 4122 Yes 11

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

  • ROA: origin9
  • ROA: none2
  • Route object: none27
  • Route object: RIR1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: origin51.241.44.0/24ROAs covering it name AS218661, not AS200260. If AS200260 should announce it, add a ROA for AS200260.2 of 673
Route object: none51.241.44.0/24Route objects for it name AS218661. Add a route object with origin AS200260 in the RIR database for the space.2 of 673
ROA: origin51.241.45.0/24ROAs covering it name AS834, not AS200260. If AS200260 should announce it, add a ROA for AS200260.2 of 673
Route object: none51.241.45.0/24Route objects for it name AS834. Add a route object with origin AS200260 in the RIR database for the space.2 of 673
ROA: origin51.241.46.0/24ROAs covering it name AS199741, not AS200260. If AS200260 should announce it, add a ROA for AS200260.2 of 673
Route object: none51.241.46.0/24Route objects for it name AS199741. Add a route object with origin AS200260 in the RIR database for the space.2 of 673
ROA: origin82.29.8.0/22ROAs covering it name AS834, not AS200260. If AS200260 should announce it, add a ROA for AS200260.2 of 673
Route object: none82.29.8.0/22Route objects for it name AS834. Add a route object with origin AS200260 in the RIR database for the space.2 of 673
ROA: origin82.29.8.0/24ROAs covering it name AS834, not AS200260. If AS200260 should announce it, add a ROA for AS200260.2 of 673
Route object: none82.29.8.0/24No route object for it. Add a route object with origin AS200260 in the RIR database for the space.2 of 673
ROA: origin82.29.9.0/24ROAs covering it name AS834, not AS200260. If AS200260 should announce it, add a ROA for AS200260.2 of 673
Route object: none82.29.9.0/24No route object for it. Add a route object with origin AS200260 in the RIR database for the space.2 of 673
ROA: origin82.29.10.0/24ROAs covering it name AS834, not AS200260. If AS200260 should announce it, add a ROA for AS200260.2 of 673
Route object: none82.29.10.0/24No route object for it. Add a route object with origin AS200260 in the RIR database for the space.2 of 673
ROA: origin82.29.11.0/24ROAs covering it name AS834, not AS200260. If AS200260 should announce it, add a ROA for AS200260.2 of 673
Route object: none82.29.11.0/24No route object for it. Add a route object with origin AS200260 in the RIR database for the space.2 of 673
ROA: origin51.241.50.0/24ROAs covering it name AS218601, not AS200260. If AS200260 should announce it, add a ROA for AS200260.1 of 673
Route object: none51.241.50.0/24Route objects for it name AS218601. Add a route object with origin AS200260 in the RIR database for the space.1 of 673
ROA: none51.241.44.0/22No ROA covers it. Add a ROA for AS200260, maxLength 22.2 of 673
Route object: none51.241.44.0/22No route object for it. Add a route object with origin AS200260 in the RIR database for the space.2 of 673
ROA: none51.241.48.0/22No ROA covers it. Add a ROA for AS200260, maxLength 22.2 of 673
Route object: none51.241.48.0/22No route object for it. Add a route object with origin AS200260 in the RIR database for the space.2 of 673
Route object: none82.29.12.0/24No route object for it. A route object for 82.29.12.0/22 with origin AS200260 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200260 in the RIR database for the space.672 of 673
Route object: none82.29.13.0/24No route object for it. A route object for 82.29.12.0/22 with origin AS200260 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200260 in the RIR database for the space.672 of 673
Route object: none82.29.14.0/24No route object for it. A route object for 82.29.12.0/22 with origin AS200260 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200260 in the RIR database for the space.672 of 673
Route object: none82.29.15.0/24No route object for it. A route object for 82.29.12.0/22 with origin AS200260 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200260 in the RIR database for the space.672 of 673
Route object: none82.39.200.0/24No route object for it. A route object for 82.39.200.0/22 with origin AS200260 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200260 in the RIR database for the space.672 of 673
Route object: none82.39.201.0/24No route object for it. A route object for 82.39.200.0/22 with origin AS200260 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200260 in the RIR database for the space.672 of 673
Route object: none82.39.202.0/24No route object for it. A route object for 82.39.200.0/22 with origin AS200260 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200260 in the RIR database for the space.672 of 673
Route object: none82.39.203.0/24No route object for it. A route object for 82.39.200.0/22 with origin AS200260 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200260 in the RIR database for the space.672 of 673
Route object: none82.110.132.0/24No route object for it. A route object for 82.110.132.0/22 with origin AS200260 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200260 in the RIR database for the space.672 of 673
Route object: none82.110.133.0/24No route object for it. A route object for 82.110.132.0/22 with origin AS200260 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200260 in the RIR database for the space.672 of 673
Route object: none82.110.134.0/24No route object for it. A route object for 82.110.132.0/22 with origin AS200260 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200260 in the RIR database for the space.672 of 673
Route object: none82.110.135.0/24No route object for it. A route object for 82.110.132.0/22 with origin AS200260 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200260 in the RIR database for the space.672 of 673
Route object: none206.208.120.0/24No route object for it. A route object for 206.208.120.0/22 with origin AS200260 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200260 in the RIR database for the space.672 of 673
Route object: none206.208.121.0/24No route object for it. A route object for 206.208.120.0/22 with origin AS200260 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200260 in the RIR database for the space.672 of 673
Route object: none206.208.122.0/24No route object for it. A route object for 206.208.120.0/22 with origin AS200260 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200260 in the RIR database for the space.672 of 673
Route object: none206.208.123.0/24No route object for it. A route object for 206.208.120.0/22 with origin AS200260 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200260 in the RIR database for the space.672 of 673
Route object: RIR82.110.132.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

2a13:75c1:100::/40RADB, RIPEValid
2a13:75c1:100::/44RIPEValid
2a13:75c1:110::/44RIPEValid
2a13:75c1:300::/40RIPEValid
2a13:75c1:3000::/36RIPEValid

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.