bgpreport

Network · data from 2026-11-12

AS47536 PathConnect

Registry name: PathConnect PathConnect GmbH, DE · PeeringDB

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

Announced routes

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

2a12:79c1:10::ffff:ffff/128 Invalid: maxLength Nonecovered by 2a12:79c1:10::/44 4 1%low visibility 9
140.235.4.0/24 Valid RIR databaseARIN 673 100% 66
185.93.174.0/24 Valid RIR databaseRIPE 673 100% 66
188.116.50.0/23 Valid RIR databaseRIPE 673 100% 66
193.105.29.0/24 Valid RIR databaseRIPE 673 100% 66
2a12:79c0::/36 Valid RIR databaseRIPE 633 100% 67
2a12:79c1::/44 Valid RIR databaseRIPE 633 100% 67
2a12:79c1:10::/44 Valid RIR databaseRIPE 633 100% 67

AS-SET

PeeringDB's irr_as_set for AS47536: AS47536:AS-PATHCONNECT. 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 (AS47536 isn't in the set, or no route object for AS47536 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 objectsAS47536 in itNot covered
AS47536:AS-PATHCONNECT RIPElists itself further down 6732779,208 Yes 1

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

  • ROA: maxLength1
  • Route object: none1
  • Route object: not announced20
ChangePrefix or setDetailFull-table peers
ROA: maxLength2a12:79c1:10::ffff:ffff/128ROA 2a12:79c1:10::/44 AS47536 has maxLength 44; ROA 2a12:79c1::/32 AS47536 has maxLength 44; the route is a /128. Raise the maxLength, or add a ROA for 2a12:79c1:10::ffff:ffff/128.4 of 636
Route object: none2a12:79c1:10::ffff:ffff/128No route object for it. A route object for 2a12:79c1:10::/44 with origin AS47536 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS47536 in the RIR database for the space.4 of 636

Route objects not announced

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

165.231.160.0/24RADBNo ROA
165.231.162.0/24RADBNo ROA
165.231.163.0/24RADBNo ROA
165.231.164.0/24RADBNo ROA
165.231.165.0/24RADBNo ROA
165.231.166.0/24RADBNo ROA
165.231.167.0/24RADBNo ROA
165.231.168.0/24RADBNo ROA
165.231.169.0/24RADBNo ROA
188.116.50.0/24RIPEInvalid: maxLength
188.116.51.0/24RIPEInvalid: maxLength
196.196.9.0/24RADBNo ROA
196.196.9.8/32RADBNo ROA
196.196.216.0/24RADBNo ROA
196.196.217.0/24RADBNo ROA
196.196.219.0/24RADBNo ROA
196.196.220.0/24RADBNo ROA
196.196.221.0/24RADBNo ROA
196.196.223.0/24RADBNo ROA
2a12:79c1:100::/44RIPEValid

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.