bgpreport

Network · data from 2026-11-12

AS34907 IP SERVICES

Registry name: IP-SERVICES-AS IP SERVICES Sp. zo.o., PL · PeeringDB

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

Announced routes

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

2a07:1340::/29 No ROA RIR databaseRIPE 634 100% 67
2a07:9240::/29 No ROA RIR databaseRIPE 634 100% 67
2a0b:7fc0::/29 No ROA RIR databaseRIPE 634 100% 67
2a11:7cc0::/29 No ROA RIR databaseRIPE 633 100% 67
2a13:9800::/29 No ROA RIR databaseRIPE 633 100% 67
2a13:a580::/29 No ROA RIR databaseRIPE 633 100% 67
2a13:c100::/29 No ROA RIR databaseRIPE 633 100% 67
2a13:ef00::/29 No ROA RIR databaseRIPE 633 100% 67
147.78.118.0/24 Valid RIR databaseRIPE 672 100% 67
185.62.1.0/24 Valid RIR databaseRIPE 672 100% 67
193.3.162.0/24 Valid RIR databaseRIPE 672 100% 67
195.245.200.0/24 Valid RIR databaseRIPE 672 100% 67
194.31.232.0/24 Valid RIR databaseRIPE 671 100% 67
2001:67c:178c::/48 Valid RIR databaseRIPE 635 100% 67
2a06:5cc0::/29 Valid RIR databaseRIPE 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS34907: AS-IP-SERVICES. 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 (AS34907 isn't in the set, or no route object for AS34907 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 objectsAS34907 in itNot covered
AS-IP-SERVICES RIPE 25177 Yes 0

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

  • ROA: none8
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2a07:1340::/29No ROA covers it. Add a ROA for AS34907, maxLength 29.634 of 636
ROA: none2a07:9240::/29No ROA covers it. Add a ROA for AS34907, maxLength 29.634 of 636
ROA: none2a0b:7fc0::/29No ROA covers it. Add a ROA for AS34907, maxLength 29.634 of 636
ROA: none2a11:7cc0::/29No ROA covers it. Add a ROA for AS34907, maxLength 29.633 of 636
ROA: none2a13:9800::/29No ROA covers it. Add a ROA for AS34907, maxLength 29.633 of 636
ROA: none2a13:a580::/29No ROA covers it. Add a ROA for AS34907, maxLength 29.633 of 636
ROA: none2a13:c100::/29No ROA covers it. Add a ROA for AS34907, maxLength 29.633 of 636
ROA: none2a13:ef00::/29No ROA covers it. Add a ROA for AS34907, maxLength 29.633 of 636

Route objects not announced

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

2a09:9000::/29RIPENo ROA
2a0e:68c0:3::/48RIPENo ROA

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.