bgpreport

Network · data from 2026-11-12

AS202934 SINCITY HOSTING

Registry name: MUNTEANU-AS SINCITY HOSTING LLC, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS202934, 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.
2a10:fa80:16::/48 No ROA None 1 0%low visibility 1
2a0b:4e07:2a0::/44 Valid None 634 100% 69
2a0b:4e07:2a2::/48 Valid None 633 100% 67
2a0b:4e07:3a::/48 Valid Other origin only 3 0%low visibility 3
2a0b:4e07:5200::/40 Valid Nonecovered by 2a0b:4e07:5000::/37 1 0%low visibility 1
185.205.33.0/24 Valid RIR databaseRADB, RIPE 653 97% 67
2a0b:4e07:5000::/37 Valid RIR databaseRIPE 634 100% 67
2a13:9500:1aa::/48 Valid RIR databaseRIPE 633 100% 69
2a13:c8c4:fc11::/48 Valid RIR databaseRIPE 633 100% 69
2a14:7580:ff97::/48 Valid RIR databaseRIPE 631 99% 70

AS-SET

PeeringDB's irr_as_set for AS202934: AS202934:AS-CUSTOMERS. 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 (AS202934 isn't in the set, or no route object for AS202934 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 objectsAS202934 in itNot covered
AS202934:AS-CUSTOMERS RIPE 4155 Yes 4

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

  • ROA: none1
  • Route object: none5
ChangePrefix or setDetailFull-table peers
ROA: none2a10:fa80:16::/48No ROA covers it. Add a ROA for AS202934, maxLength 48.1 of 636
Route object: none2a10:fa80:16::/48No route object for it. Add a route object with origin AS202934 in the RIR database for the space.1 of 636
Route object: none2a0b:4e07:2a0::/44No route object for it. Add a route object with origin AS202934 in the RIR database for the space.634 of 636
Route object: none2a0b:4e07:2a2::/48No route object for it. Add a route object with origin AS202934 in the RIR database for the space.633 of 636
Route object: none2a0b:4e07:3a::/48Route objects for it name AS202954. Add a route object with origin AS202934 in the RIR database for the space.3 of 636
Route object: none2a0b:4e07:5200::/40No route object for it. A route object for 2a0b:4e07:5000::/37 with origin AS202934 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202934 in the RIR database for the space.1 of 636

Route objects not announced

Every route object with origin AS202934 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.