bgpreport

Network · data from 2026-11-12

AS47556 WEBTIT Webtitude LTD

Registry name: WEBTIT Webtitude LTD, GB · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS47556, 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:a840::/32 No ROA Nonecovered by 2a12:a840::/29 635 100% 69
2a12:a841::/32 No ROA Nonecovered by 2a12:a840::/29 635 100% 69
2a12:a842::/32 No ROA Nonecovered by 2a12:a840::/29 634 100% 67
2a12:a843::/32 No ROA Nonecovered by 2a12:a840::/29 603 95% 67
2a12:a844::/32 No ROA Nonecovered by 2a12:a840::/29 603 95% 67
45.140.96.0/22 No ROA RIR databaseRIPE 672 100% 67

AS-SET

AS47556 isn't in PeeringDB, where networks name their AS-SET.

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

  • ROA: none6
  • Route object: none5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2a12:a840::/32No ROA covers it. Add a ROA for AS47556, maxLength 32.635 of 636
Route object: none2a12:a840::/32No route object for it. A route object for 2a12:a840::/29 with origin AS47556 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47556 in the RIR database for the space.635 of 636
ROA: none2a12:a841::/32No ROA covers it. Add a ROA for AS47556, maxLength 32.635 of 636
Route object: none2a12:a841::/32No route object for it. A route object for 2a12:a840::/29 with origin AS47556 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47556 in the RIR database for the space.635 of 636
ROA: none2a12:a842::/32No ROA covers it. Add a ROA for AS47556, maxLength 32.634 of 636
Route object: none2a12:a842::/32No route object for it. A route object for 2a12:a840::/29 with origin AS47556 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47556 in the RIR database for the space.634 of 636
ROA: none2a12:a843::/32No ROA covers it. Add a ROA for AS47556, maxLength 32.603 of 636
Route object: none2a12:a843::/32No route object for it. A route object for 2a12:a840::/29 with origin AS47556 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47556 in the RIR database for the space.603 of 636
ROA: none2a12:a844::/32No ROA covers it. Add a ROA for AS47556, maxLength 32.603 of 636
Route object: none2a12:a844::/32No route object for it. A route object for 2a12:a840::/29 with origin AS47556 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47556 in the RIR database for the space.603 of 636
ROA: none45.140.96.0/22No ROA covers it. Add a ROA for AS47556, maxLength 22.672 of 673

Route objects not announced

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

2a12:a840::/29RIPENo 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.